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

feat: apply CRD at built time if quarkus.operator-sdk.crd.apply=true #260

Merged
merged 1 commit into from
Mar 11, 2022

Conversation

Sgitario
Copy link
Contributor

@Sgitario Sgitario commented Mar 7, 2022

When enabling quarkus.operator-sdk.crd.apply=true at build time, we will register the CRD in the Kubernetes cluster where user is logged in.

Updated documentation and added a note saying that this will always be done when running the application on Dev mode.

Fix #242

When enabling `quarkus.operator-sdk.crd.apply=true` at build time, we will register the CRD in the Kubernetes cluster where user is logged in. 

Updated documentation and added a note saying that this will always be done when running the application on Dev mode.

Fix quarkiverse#242
@Sgitario Sgitario requested a review from metacosm March 9, 2022 06:21
Copy link
Member

@metacosm metacosm left a comment

Choose a reason for hiding this comment

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

LGTM

@metacosm metacosm merged commit 41a08c5 into quarkiverse:next Mar 11, 2022
@Sgitario Sgitario deleted the feat_crd_apply branch March 14, 2022 06:02
metacosm pushed a commit that referenced this pull request Mar 30, 2022
#260)

When enabling `quarkus.operator-sdk.crd.apply=true` at build time, we will register the CRD in the Kubernetes cluster where user is logged in.

Updated documentation and added a note saying that this will always be done when running the application on Dev mode.

Fixes #242
metacosm pushed a commit that referenced this pull request Apr 1, 2022
#260)

When enabling `quarkus.operator-sdk.crd.apply=true` at build time, we will register the CRD in the Kubernetes cluster where user is logged in.

Updated documentation and added a note saying that this will always be done when running the application on Dev mode.

Fixes #242
metacosm added a commit that referenced this pull request Jan 6, 2023
The rationale for this is that there's really no point in applying the
CRDs at build time to a cluster that might not be the one where the code
will run. Moreover, this also meant that CRDs would be applied twice.

This reverts the behavior introduced by #260.
metacosm added a commit that referenced this pull request Jan 6, 2023
Fixes #455.

The rationale for this is that there's really no point in applying the
CRDs at build time to a cluster that might not be the one where the code
will run. Moreover, this also meant that CRDs would be applied twice.

This reverts the behavior introduced by #260.
metacosm added a commit that referenced this pull request Jan 6, 2023
Fixes #455.

The rationale for this is that there's really no point in applying the
CRDs at build time to a cluster that might not be the one where the code
will run. Moreover, this also meant that CRDs would be applied twice.

This reverts the behavior introduced by #260.
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