Skip to content
This repository has been archived by the owner on Apr 11, 2024. It is now read-only.

feat: Add examples for Nutanix provider #5

Merged
merged 8 commits into from
Mar 28, 2024
Merged

feat: Add examples for Nutanix provider #5

merged 8 commits into from
Mar 28, 2024

Conversation

deepakm-ntnx
Copy link

@deepakm-ntnx deepakm-ntnx commented Mar 21, 2024

added nutanix examples for clusterclass and cluster

hack/examples/sync.sh Outdated Show resolved Hide resolved
@deepakm-ntnx deepakm-ntnx changed the title Nutanix examples feat: Add examples for Nutanix provider Mar 22, 2024
devbox.lock Outdated Show resolved Hide resolved
hack/examples/patches/nutanix/initialize-variables.yaml Outdated Show resolved Hide resolved
@deepakm-ntnx
Copy link
Author

@jimmidyson @faiq @dkoshkin @thunderboltsid any more comments? can we merge this?

Copy link
Member

@jimmidyson jimmidyson left a comment

Choose a reason for hiding this comment

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

Some comments but this is very close to being merged! Great work @deepakm-ntnx!

@faiq
Copy link

faiq commented Mar 27, 2024

For now, I think it would be better to have non-working minimal examples here and later down the line adding the proper code in the form of GeneratePatch hooks and Lifecycle hooks to get started.

@deepakm-ntnx
Copy link
Author

For now, I think it would be better to have non-working minimal examples here and later down the line adding the proper code in the form of GeneratePatch hooks and Lifecycle hooks to get started.

yes thats the plan if i understand your comment correctly. is it not the case in this PR?

Copy link
Collaborator

@dkoshkin dkoshkin left a comment

Choose a reason for hiding this comment

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

Thanks for the tickets @deepakm-ntnx.
I'm good with merging this as is and working on those follow up tickets, but I will let @faiq and @jimmidyson do the actual approvals since they left the original comments.

@deepakm-ntnx
Copy link
Author

For now, I think it would be better to have non-working minimal examples here and later down the line adding the proper code in the form of GeneratePatch hooks and Lifecycle hooks to get started.

yes thats the plan if i understand your comment correctly. is it not the case in this PR?

we will remove ccm related things from the cluster-topology example yaml once we move ccm installation as addon thru post cluster creation step in ccm https://d2iq.atlassian.net/browse/D2IQ-99841

faiq
faiq previously requested changes Mar 27, 2024
Copy link

@faiq faiq left a comment

Choose a reason for hiding this comment

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

I strongly prefer to remove the CCM cluster resource sets from the examples.

I can live with the rest of the stuff not being patches.

@deepakm-ntnx
Copy link
Author

I strongly prefer to remove the CCM cluster resource sets from the examples.

I can live with the rest of the stuff not being patches.

could you please add more details on why you feel so strongly? would it not be ok with you if we do it thru above mentioned tracker? i think this is really minor change and does not really add value. mainly https://d2iq.atlassian.net/browse/D2IQ-99841. given we are still in dev phase, we should run in iterations. cc @jimmidyson

@jimmidyson
Copy link
Member

While I would prefer CCM to be added as an addon at this point, to keep this moving and to make it possible to create a Nutanix cluster using CAREN hooks, I agree we should merge this once it's working and do the refactoring as a follow up. This will unblock other work, such as testing Nutanix CSI, etc, and allow adding e2e tests, etc.

@faiq
Copy link

faiq commented Mar 28, 2024

While I would prefer CCM to be added as an addon at this point, to keep this moving and to make it possible to create a Nutanix cluster using CAREN hooks, I agree we should merge this once it's working and do the refactoring as a follow up. This will unblock other work, such as testing Nutanix CSI, etc, and allow adding e2e tests, etc.

We don't need CCM to be enabled to be able to test CSI. We could simply test if the pods will come up on the first control plane node.

@jimmidyson
Copy link
Member

We don't need CCM to be enabled to be able to test CSI.

OK but CCM is required to bring a cluster fully up and make all nodes ready so it is still a blocker for e2e tests for Nutanix provider for example.

@faiq
Copy link

faiq commented Mar 28, 2024

OK but CCM is required to bring a cluster fully up and make all nodes ready so it is still a blocker for e2e tests for Nutanix provider for example.

tests should fail until the code is complete.

@jimmidyson jimmidyson self-requested a review March 28, 2024 17:33
@jimmidyson jimmidyson dismissed their stale review March 28, 2024 17:33

Unblocking

@faiq faiq dismissed their stale review March 28, 2024 17:41

unblocking

@faiq faiq enabled auto-merge March 28, 2024 17:42
@faiq faiq merged commit 554dacd into main Mar 28, 2024
16 checks passed
@faiq faiq deleted the nutanix-examples branch March 28, 2024 21:35
@github-actions github-actions bot mentioned this pull request Mar 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants