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

controller: Ensure the runtimeclass was created by the payload #245

Conversation

fidencio
Copy link
Member

36664b5 introduced a regression as the runtimeClass creation was left to the runtime payload, but we never checked whether this actually was created neither updated the status on the Operator side.

jepio and others added 4 commits August 10, 2023 11:51
The 'kustomize edit set image' step needs to specify the correct 'name' to
override before the '=' sign otherwise it only overrides the tag for the image.
The previous version results in this entry (which does nothing to the manifest)

images:
- name: localhost:5000/cc-operator
  newTag: latest

and the new version does this:

images:
- name: quay.io/confidential-containers/operator
  newName: localhost:5000/cc-operator
  newTag: latest

The 'name' needs to be the quay entry and not 'controller' because there is
already a previous override in config/manager/kustomization.yaml.

Signed-off-by: Jeremi Piotrowski <jpiotrowski@microsoft.com>
The kind cluster is connected to a different bridge than the registry , which
means the kind cluster can't pull from 'localhost:5000'. Connect the registry
to the same kind bridge and use the container name as a mirror for 'localhost'
so that pulling works.

Signed-off-by: Jeremi Piotrowski <jpiotrowski@microsoft.com>
Signed-off-by: Jeremi Piotrowski <jpiotrowski@microsoft.com>
36664b5 introduced a regression as the
runtimeClass creation was left to the runtime payload, but we never
checked whether this actually was created neither updated the status on
the Operator side.

Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>
@fidencio fidencio force-pushed the topic/fix-empty-runtime-class-status branch from a4aba3f to fbc66fb Compare August 10, 2023 11:05
@fidencio fidencio mentioned this pull request Aug 10, 2023
@fidencio fidencio closed this Aug 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants