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

Add release manifest to Giant Swarm specific image so cluster-api-provider-aws-app can fetch CRDs from there instead of having to use GitHub releases #425

Merged
merged 1 commit into from
Feb 8, 2023

Conversation

AndiDog
Copy link

@AndiDog AndiDog commented Feb 2, 2023

Towards giantswarm/roadmap#1832

Since we don't use GitHub releases from which we could fetch the relevant file with CRDs (infrastructure-components.yaml), I thought of simply adding that file to the image. This way, the app repo https://github.com/giantswarm/cluster-api-provider-aws-app can be adapted very easily to get the CRDs from the correct commit of our CAPA fork.

This is to avoid mismatches between CRD and controller version.

I have the matching change to cluster-api-provider-aws-app ready, but won't open that PR yet since we're blocked on upgrading CAPA (giantswarm/roadmap#1932).

…ovider-aws-app` can fetch CRDs from there instead of having to use GitHub releases
@AndiDog
Copy link
Author

AndiDog commented Feb 8, 2023

Guess this is fine, based on offline discussion

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.

1 participant