Skip to content

reconsider ConstraintTemplate status placement #367

@acpana

Description

@acpana

It seems that the ConstraintTemplatePodStatus could be better homed in Gatekeeper:

// CreateCRDError represents a single error caught during parsing, compiling, etc.
type CreateCRDError struct {
Code string `json:"code"`
Message string `json:"message"`
Location string `json:"location,omitempty"`
}
// ByPodStatus defines the observed state of ConstraintTemplate as seen by
// an individual controller.
type ByPodStatus struct {
// a unique identifier for the pod that wrote the status
ID string `json:"id,omitempty"`
ObservedGeneration int64 `json:"observedGeneration,omitempty"`
Errors []CreateCRDError `json:"errors,omitempty"`
}
// ConstraintTemplateStatus defines the observed state of ConstraintTemplate.
type ConstraintTemplateStatus struct {
Created bool `json:"created,omitempty"`
ByPod []ByPodStatus `json:"byPod,omitempty"`
// INSERT ADDITIONAL STATUS FIELD - define observed state of cluster
// Important: Run "make" to regenerate code after modifying this file
}

If that's possible we should consider making that change.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions