-
Notifications
You must be signed in to change notification settings - Fork 0
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
Attach release manifests for clusterctl #30
base: main
Are you sure you want to change the base?
Conversation
b752b2b
to
a5a2d21
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks that the other cluster API providers put their cluster-template.yaml
into <rootDir>/templates/
.
- env: | ||
- name: METAL_API_URL | ||
valueFrom: | ||
secretKeyRef: | ||
name: controller-manager-config |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The indentation is inconsistent with the other files!
@@ -4,5 +4,5 @@ apiVersion: kustomize.config.k8s.io/v1beta1 | |||
kind: Kustomization | |||
images: | |||
- name: controller | |||
newName: capms-controller | |||
newTag: latest | |||
newName: ghcr.io/metal-stack/capms-controller |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
newName: ghcr.io/metal-stack/capms-controller | |
newName: ghcr.io/metal-stack/cluster-api-metal-stack-controller |
Description
For the previous release we hand-rolled this process
Closes #23
Closes #29
Here I attach all manifests at the release draft although there will be no tagged image yet. This way we can observe the behavior of the actual release process beforehand.