Conversation
| pfRunnerImage: quay.io/ibm-aiu/x86_64/release/dd2/spyredriver-image:latest | ||
| spyreFilter: . | ||
| vfRunnerImage: quay.io/ibm-aiu/x86_64/release/dd2/spyredriver-image:latest |
There was a problem hiding this comment.
Is it good to use latest?.
Isnt it better to use a specific version tag that we have tested so that we dont have to worry if there is any future release breaking changes?
There was a problem hiding this comment.
True @mayuka-c
Currently the repo is private and I can't see what the latest tag is pointing to.
When I create a SpyreClusterPolicy, it default to the latest tag
|
Can we have the path as This would align with out app path |
Signed-off-by: Sathvik <Sathvik.S@ibm.com>
Signed-off-by: Sathvik <Sathvik.S@ibm.com>
Signed-off-by: Sathvik <Sathvik.S@ibm.com>
Signed-off-by: Sathvik <Sathvik.S@ibm.com>
sats-23
force-pushed
the
bs-manifests
branch
from
0508fe6 to
6c2e914
Compare
mkumatag
left a comment
mkumatag
left a comment
There was a problem hiding this comment.
whats the relevant directory we need to name? is bootstrap a right thing? or can we rename to something else like internal, .system or something else which make sense for the tool itself.?
also we need to add an entry in here as well to include these newly added asset
| sourceNamespace: openshift-marketplace | ||
| startingCSV: spyre-operator.v1.1.1 | ||
| --- | ||
| apiVersion: spyre.ibm.com/v1alpha1 |
There was a problem hiding this comment.
we shouldn't do this, we should just add a patch to the existing resource gets deployed by default to remove that one unwanted entry from the existing resource.
There was a problem hiding this comment.
let us names the files like 00-, 02- etc..
| kubernetes.io/arch: ppc64le | ||
| machineconfiguration.openshift.io/role: spyre |
There was a problem hiding this comment.
lets have some labels across all the machineconfigs, e.g: kubernetes.io/arch: ppc64le exist only in this and doesn't in other 2 machineconfigs
3 participants
Manifests that will be used in bootstrap configure process.
Contains:
Dependent Operators
--Node Feature Discovery w/ CR NFD
--Cert-Manager w/ CR Self-Signed Issuer, CA Certificate, CA Issuer, Webhook Certificate
--Service Mesh 3
--Secondary Scheduler
Machine Config (numbered for the ordering) - reference
--Machine Config Pool
--Actual MachineConfig for spyre configuration
Core Operators
--Spyre Operator w/ CR SpyreClusterPolicy (w/o externalDeviceReservation)
RHOAI Operator will be included eventually after v3.3.0 is GA'ed