Environment variable handling and CRD updates - Githubissues

networkservicemesh / nsm-operator

A kubernetes operator for deploying and managing Network Service Meshes

Apache License 2.0

9 stars 8 forks source link

Environment variable handling and CRD updates #67

Closed szvincze closed 1 year ago

szvincze commented 1 year ago

Makefile:

The ci-yaml generation fixed, a missing separator inserted, roles and binding for admission-webhook-k8s added.

CRD:

Replica count parameter is added to Registry
spireAgentSocket is added to NSM level parameters
nsmPullPolicy is not required because we use default

Handling of environment variables fixed and extended:

Every components can handle environment variables coming from CR
If spireAgentSocket is defined in the CR then it will be used from there even if SPIFFE_ENDPOINT_SOCKET is given as environment variable or default is used.

Registry:

The reconciler can update the registry deployment in case the replica count changed in the CR.