Skip to content

Missing fields in CRD status section #772

@barney-s

Description

@barney-s

Description

Observed Behavior:

When i set the RGD schema status to

    status:
      # Fields the controller will inject into instances status.
      draft: string
      userDraft: string
      fqdn: ${service.metadata.name}.${service.metadata.namespace}.svc.cluster.local
      conditions: ${pod.status.conditions}

i see this generated in the CRD :

status:
            properties:
              conditions:
                items:
                  properties:
                    lastTransitionTime:
                      type: string
                    message:
                      type: string
                    observedGeneration:
                      type: integer
                    reason:
                      type: string
                    status:
                      type: string
                    type:
                      type: string
                  type: object
                type: array
              fqdn:
                type: string
             conditions:
                items:
                  properties:
                    lastTransitionTime:
                      type: string
                    message:
                      type: string
                    observedGeneration:
                      type: integer
                    reason:
                      type: string
                    status:
                      type: string
                    type:
                      type: string
                  type: object
                type: array
              state:
                type: string

Expected Behavior:

Expect to see draft and userDraft in status fields.

Reproduction Steps (Please include ResourceGraphDefinition and Instances files):

Versions:

  • kro version: 0.5.1
  • Kubernetes Version (kubectl version):
 % kubectl version    
Client Version: v1.33.5-dispatcher
Kustomize Version: v5.6.0
Server Version: v1.27.3
  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Which option describes the most your issue?

No response

Metadata

Metadata

Labels

kind/bugCategorizes issue or PR as related to a bug.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions