Repository navigation
Fix conflict of deploying KubeVirt Instancetypes - #691
Conversation
WalkthroughThis pull request updates an identifier in a Makefile and introduces a new configuration option in a YAML file. The Makefile change involves updating the exported variable Changes
Sequence Diagram(s)sequenceDiagram
participant U as User
participant C as Config Loader
participant D as Deployment Manager
U->>C: Submit kubevirt-cr.yaml with new config
C->>D: Parse spec.configuration.commonInstancetypesDeployment
alt commonInstancetypesDeployment enabled=true
D->>D: Deploy common instance types
else commonInstancetypesDeployment enabled=false
D->>D: Skip deployment of common instance types
end
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
🧰 Additional context used🪛 GitHub Actions: Pre-Commit Checkspackages/system/kubevirt-instancetypes/Makefile[error] 4-4: Command failed with exit code 1 during 'make generate'. Error: ENOENT: no such file or directory, open 'values.yaml' [error] 8-8: Command failed with exit code 1 during 'make generate'. Error: ERROR: error getting current Parameters section from README 🔇 Additional comments (2)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
We have common-instance-types deployed by kubevirt-operator and separate helm-chart.
In this case operator always overrides the resource by default ones.
This PR disables common-instance-types deployment for kubevirt-operator
Summary by CodeRabbit
Chores
New Features