You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps did you take and what happened:
Create a kind cluster and install CAPC on it. Attempting to serialize a CloudStackMachineTemplate resource and then apply the result to a K8s cluster. This returned the following error:
"error: error validating \"STDIN\": error validating data: unknown object type \"nil\" in CloudStackMachineTemplate.spec.template.metadata.creationTimestamp; if you choose to ignore these errors, turn validation off with --validate=false\n"
What did you expect to happen:
I expected to be able to serialize the Go object to bytes, and then apply it with kubectl without having an extra ObjectMeta resource included to worry about. This ObjectMeta does not appear to be used anywhere in CAPC and should be removed. I should not have to set the creationTimestamp field either since as the comment says
// CreationTimestamp is a timestamp representing the server time when this object was
// created. It is not guaranteed to be set in happens-before order across separate operations.
// Clients may not set this value. It is represented in RFC3339 form and is in UTC.
Anything else you would like to add:
This ObjectMeta does not appear to be used anywhere in CAPC and should be removed. However, this would require a new CAPC api version bump
Environment:
Cluster-api-provider-cloudstack version: main
Kubernetes version: (use kubectl version): 1.21
OS (e.g. from /etc/os-release):
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
/kind bug
What steps did you take and what happened:
Create a kind cluster and install CAPC on it. Attempting to serialize a CloudStackMachineTemplate resource and then apply the result to a K8s cluster. This returned the following error:
It's basically causing the issue described in kubernetes/kubernetes#67610
What did you expect to happen:
I expected to be able to serialize the Go object to bytes, and then apply it with kubectl without having an extra ObjectMeta resource included to worry about. This ObjectMeta does not appear to be used anywhere in CAPC and should be removed. I should not have to set the creationTimestamp field either since as the comment says
Anything else you would like to add:
This ObjectMeta does not appear to be used anywhere in CAPC and should be removed. However, this would require a new CAPC api version bump
Environment:
kubectl version
): 1.21/etc/os-release
):The text was updated successfully, but these errors were encountered: