Skip to content

Metadata fields are not handled correctly by Kubernetes #210

@ricardozanini

Description

@ricardozanini

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:

Metadata

Metadata

Assignees

No one assigned

    Labels

    bug 🐛Something isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy