Skip to content
This repository was archived by the owner on Aug 12, 2025. It is now read-only.

Conversation

@gianarb
Copy link
Contributor

@gianarb gianarb commented May 5, 2020

It does not look like the PacketMachine needs a ProjectID. It is a value
that we get from the PacketCluster.

It is not even generated from the make examples file and when applied
via kubectl it fails because PachetMachine.ProjectID is a required field
in openapi.

It does not look like the PacketMachine needs a ProjectID. It is a value
that we get from the PacketCluster.

It is not even generated from the `make examples` file and when applied
via kubectl it fails because PachetMachine.ProjectID is a required field
in openapi.
@gianarb
Copy link
Contributor Author

gianarb commented May 5, 2020

@deitch can you validate my assumption and the change itself?
Thanks a lot

@deitch
Copy link
Contributor

deitch commented May 5, 2020

It does not look like the PacketMachine needs a ProjectID. It is a value
that we get from the PacketCluster.

I think you are correct. I am looking at the change itself.

Copy link
Contributor

@deitch deitch left a comment

Choose a reason for hiding this comment

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

That looks right.

@deitch
Copy link
Contributor

deitch commented May 5, 2020

I approved the PR, but it looks like CI is failing due to some weird controller-gen stuff. Since this is a development branch, it isn't worth holding it up, but we should get that fixed too.

@deitch deitch merged commit ec6b1ee into kubernetes-retired:v1alpha3 May 5, 2020
@gianarb gianarb deleted the fix/packet-machine-crd-spec-projectID branch May 5, 2020 10:41
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants