v1.16.0

Ansible-based operators: add resource limits

Add into the config/manager/manager.yaml the following limits which are now scaffolded by default:

 ... 
 # TODO(user): Configure the resources accordingly based on the project requirements. # More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ resources:
  limits:
    cpu: 500m
    memory: 768Mi
  requests:
    cpu: 10m
    memory: 256Mi

IMPORTANT: Having resource limits is a best-practice and these values are reasonable defaults, but Operator authors should optimize these values based on their project’s requirements.

See #5274 for more details.

Bump operator_sdk.util in requirements.yml

Update requirements.yml to point to 0.3.1 of operator_sdk.util instead of 0.2.0

See #5462 for more details.

Add annotation to specify the default container

Add the following annotation into the file config/manager/manager.yaml

...
template:
  metadata:
    annotations:
      kubectl.kubernetes.io/default-container: manager
...

See #5330 for more details.

Add PHONY targets to Makefile

Add PHONY target to all Makefile targets. For example, refer to the Makefile in operator-sdk/testdata directory of OperatorSDK tagged by the release containing this change.

See #5330 for more details.

For Golang-based projects, add the flag ignore-not-found into the Makefile for the uninstall and undeploy targets

Update the Makefile with the following changes.

1. Above ##@ Deployment add the following:

...
ifndef ignore-not-found
  ignore-not-found = false
endif
...

1. Replace: sh kubectl delete -f - With: sh kubectl delete --ignore-not-found=$(ignore-not-found) -f -

NOTE You can also compare your Makefile with the one tagged by this release, in operator-sdk/testdata of the OperatorSDK project.

See #5330 for more details.

Last modified January 14, 2022: Migration guide generation improvements (#5494) (43b5394c)