Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Metadata fields are not handled correctly by Kubernetes #210

Closed
ricardozanini opened this issue Oct 8, 2024 · 0 comments · Fixed by #211
Closed

Metadata fields are not handled correctly by Kubernetes #210

ricardozanini opened this issue Oct 8, 2024 · 0 comments · Fixed by #211
Labels
bug 🐛 Something isn't working

Comments

@ricardozanini
Copy link
Member

What happened:
When running the SDK with Kubernetes API, the admission controller won't parse metadata fields correctly. This happens because it's a dynamic object that can be anything. This way, the admission controller won't know how to handle these objects.

What you expected to happen:
That metadata fields are preserved when a CRD using this SDK is submitted to the server.

How to reproduce it:
Add a metadata field to a workflow state (v0.8/v0.9):

"states": [
    {
      "name": "CheckApplication",
      "type": "switch",
      "metadata": {
        "metadataState": "state info"
      },

Anything else we need to know?:
See context here:

@ricardozanini ricardozanini added the bug 🐛 Something isn't working label Oct 8, 2024
ricardozanini added a commit to ricardozanini/sdk-go that referenced this issue Oct 8, 2024
…metadata fields

Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant