Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert "Backend Samples: place on worker nodes" #335

Merged

Conversation

Akrog
Copy link
Contributor

@Akrog Akrog commented Feb 13, 2024

This reverts commit 9ef753e, where we tried to pin the MachineConfig to the worker role, because they don't work.

Even if the OpenShift CRC node has both master and worker roles, that doesn't mean that we can use them for the MachineConfig, because the thing that ties together a MachineConfig to a Machine is the MachineConfigPool and a Machine can only belong to one MachineConfigPool.

And looking at the available Machine in a CRC deployment we see that it has the master role.

Name:         crc-ksq4m-master-0
Namespace:    openshift-machine-api
Labels:       machine.openshift.io/cluster-api-cluster=crc-ksq4m
              machine.openshift.io/cluster-api-machine-role=master
              machine.openshift.io/cluster-api-machine-type=master

And looking at the MachineConfigPool we see that only the master pool has machine assigned to it.

NAME     CONFIG                                             UPDATED   UPDATING   DEGRADED   MACHINECOUNT   READYMACHINECOUNT   UPDATEDMACHINECOUNT   DEGRADEDMACHINECOUNT   AGE
master   rendered-master-e542525f4afc269344cc5e648a41f812   True      False      False      1              1                   1                     0                      34d
worker   rendered-worker-c36181deab728b3d19199b5b7dd30332   True      False      False      0              0                   0                     0                      34d

This reverts commit 9ef753e, where we
tried to pin the `MachineConfig` to the `worker` role, because they
don't work.

Even if the OpenShift CRC node has both master and worker roles, that
doesn't mean that we can use them for the `MachineConfig`, because the
thing that ties together a `MachineConfig` to a `Machine` is the
`MachineConfigPool` and a `Machine` can only belong to one
`MachineConfigPool`.

And looking at the available `Machine` in a CRC deployment we see that it
has the master role.

```
Name:         crc-ksq4m-master-0
Namespace:    openshift-machine-api
Labels:       machine.openshift.io/cluster-api-cluster=crc-ksq4m
              machine.openshift.io/cluster-api-machine-role=master
              machine.openshift.io/cluster-api-machine-type=master
```

And looking at the `MachineConfigPool` we see that only the `master`
pool has machine assigned to it.

```
NAME     CONFIG                                             UPDATED   UPDATING   DEGRADED   MACHINECOUNT   READYMACHINECOUNT   UPDATEDMACHINECOUNT   DEGRADEDMACHINECOUNT   AGE
master   rendered-master-e542525f4afc269344cc5e648a41f812   True      False      False      1              1                   1                     0                      34d
worker   rendered-worker-c36181deab728b3d19199b5b7dd30332   True      False      False      0              0                   0                     0                      34d
```
Copy link
Contributor

@ASBishop ASBishop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Copy link
Contributor

openshift-ci bot commented Feb 13, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Akrog, ASBishop

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 98deddd into openstack-k8s-operators:main Feb 13, 2024
7 checks passed
@Akrog Akrog deleted the rever-samples-worker branch February 20, 2024 10:33
ASBishop pushed a commit to ASBishop/cinder-operator that referenced this pull request Mar 11, 2024
…rators/renovate/openstack-k8s-operators

Update openstack-k8s-operators
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants