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
API Group a set of resources that are exposed together. Along with the version is exposed in the "apiVersion" field as "GROUP/VERSION", e.g. "policy.k8s.io/v1".
Current involvedObject.apiVersion field in Workflow Event contains only version value v1alpha but the group value must also be added: argoproj.io/v1alpha1.
What you expected to happen:
involvedObject.apiVersion field in both Workflow Event and Workflow Node Event must conform Kubernetes API conventions as mentioned above.
How to reproduce it (as minimally and precisely as possible):
Run workflow and let the workflow-controller emit Workflow Event or Workflow Node Event.
Anything else we need to know?:
This issue leads to ambiguous apiVersion/Kind if the same kind name with different group exists in the Kubernetes cluster.
Environment:
Argo version: 2.8.0-rc4
$ argo version
Kubernetes version : 1.15.3
$ kubectl version -o yaml
Other debugging information (if applicable):
Workflow Event resource log.
apiVersion: v1kind: Eventmetadata:
creationTimestamp: "2020-05-05T11:50:00Z"name: dag-sample-6r244.160c1f7f62cb9ce6namespace: sampleresourceVersion: "147231006"selfLink: /api/v1/namespaces/sample/events/dag-sample-6r244.160c1f7f62cb9ce6uid: 38026c89-bea5-46dc-bce2-1887ac93b163involvedObject:
# apiVersion is not following API convention: "GROUP/VERSION"apiVersion: v1alpha1kind: Workflowname: dag-sample-6r244namespace: sampleresourceVersion: "147231005"uid: 39aa113f-b48a-4e3d-ad13-0e9d639e06c6count: 1eventTime: nullfirstTimestamp: "2020-05-05T11:50:00Z"lastTimestamp: "2020-05-05T11:50:00Z"message: Workflow Runningreason: WorkflowRunningreportingComponent: ""reportingInstance: ""source:
component: dag-sample-6r244type: Normal
Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered:
Checklist:
What happened:
involvedObject.apiVersion
field in both Workflow Event and Workflow Node Event violates Kubernetes API conventions.https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md
Current
involvedObject.apiVersion
field in Workflow Event contains only version valuev1alpha
but the group value must also be added:argoproj.io/v1alpha1
.What you expected to happen:
involvedObject.apiVersion
field in both Workflow Event and Workflow Node Event must conform Kubernetes API conventions as mentioned above.How to reproduce it (as minimally and precisely as possible):
Run workflow and let the workflow-controller emit Workflow Event or Workflow Node Event.
Anything else we need to know?:
This issue leads to ambiguous apiVersion/Kind if the same kind name with different group exists in the Kubernetes cluster.
Environment:
Other debugging information (if applicable):
Workflow Event resource log.
Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: