Introduce MachineSet scale test - #162
Conversation
| let client = self.test_ctx.client(); | ||
| let machine_name = &self.machine_name; | ||
|
|
||
| self.test_ctx.info("Cleaning up"); |
There was a problem hiding this comment.
Perhaps start with setting replicas=0 for the machine-set (or is it done as part of the tests?)
There was a problem hiding this comment.
Good point, have added
| spec: MachineConfigSpec { | ||
| os_image_url: Some(bootc_image), | ||
| ..Default::default() | ||
| }, |
There was a problem hiding this comment.
Wasn't there one more required configuration for a machine to become a node -- such that OpenShift accepts the custom RHCOS image ?
There was a problem hiding this comment.
None that I remember, but I can't really test it right now
| test_ctx.info("Updating MachineSet replicas to 0"); | ||
| let rp = Default::default(); | ||
| machinesets.replace(machine_name, &rp, &mset).await?; | ||
| scale_ctx.has_replicas(0, scaled_duration(60)).await?; |
There was a problem hiding this comment.
nit: in a later PR we can write a function to update the machineset replicas (and possibly another one that also waits for the replicas to come up)
uril
left a comment
There was a problem hiding this comment.
Looks good to me, with some comments
1920336 to
2e9723b
Compare
132dd36 to
7e7133d
Compare
e90051d to
346ffd6
Compare
accounting for Containerfile unification, bumping buildroot Signed-off-by: Jakob Naucke <jnaucke@redhat.com> Assisted-by: AI
Signed-off-by: Jakob Naucke <jnaucke@redhat.com> Assisted-by: AI
Create MachineConfig, MachineConfigPool & MachineSet. Includes pluggable modules for TEE platforms, and Azure as a first module. Test with 1 & 2 replicas. Test with a replica after deletion. Operator components are deployed in the same cluster, i.e. no bootstrap functionality. Will not work until coreos/fedora-coreos-tracker#2191 is resolved, but already gets to Azure machine creation (with no ignition) in this state. Signed-off-by: Jakob Naucke <jnaucke@redhat.com> Assisted-by: AI
has an incompatible validation rule Signed-off-by: Jakob Naucke <jnaucke@redhat.com> Assisted-by: AI
346ffd6 to
2660e54
Compare
|
Now that a single Containerfile is used, 'build_target' must be passed to buildah. |
| ARG build_target=operator | ||
|
|
||
| # Unified builder stage, compiles all binaries in a single cargo invocation. | ||
| FROM quay.io/redhat-user-workloads/cocl-operator-tenant/buildroot@sha256:34806c0eb874b00bcd0fc90241746404e051070b278ac0351e5c8873ffda8b39 |
I added a fix for that in #166 |
Create MachineConfig, MachineConfigPool & MachineSet. Includes pluggable modules for TEE platforms, and Azure as a first module.
Test with 1 & 2 replicas. Test with a replica after deletion.
Operator components are deployed in the same cluster, i.e. no bootstrap functionality.
Will not work until coreos/fedora-coreos-tracker#2191 is resolved, but already gets to Azure machine creation (with no ignition) in this state.
In a separate, revertable commit, add a workaround for openshift/api#2978.
Before that, update operator and drift cache. Add a skill to do so.
Bundle build is expected to fail until trusted-execution-clusters/operator#337 is merged and can be pulled in.