operator kubernetes-nmstate-operator (0.88.0)

[mkowalski]

kubernetes-nmstate-operator version 0.88.0

This PR adds version 0.88.0 of the kubernetes-nmstate-operator to OperatorHub.

Changes

• Operator version: 0.88.0
• Handler image: quay.io/nmstate/kubernetes-nmstate-handler:v0.88.0
• Operator image: quay.io/nmstate/kubernetes-nmstate-operator:v0.88.0

Checklist

• Bundle manifests generated and validated
• Image tags updated to v0.88.0
• Pull policy set to IfNotPresent

This PR was automatically generated by the kubernetes-nmstate release process.

/kind operator
/area provider/kubernetes

[openshift-ci]

@mkowalski: The label(s) kind/operator, area/provider/kubernetes cannot be applied, because the repository doesn't have them.

In response to this:

kubernetes-nmstate-operator version 0.88.0

This PR adds version 0.88.0 of the kubernetes-nmstate-operator to OperatorHub.

Changes

• Operator version: 0.88.0
• Handler image: quay.io/nmstate/kubernetes-nmstate-handler:v0.88.0
• Operator image: quay.io/nmstate/kubernetes-nmstate-operator:v0.88.0

Checklist

• Bundle manifests generated and validated
• Image tags updated to v0.88.0
• Pull policy set to IfNotPresent

This PR was automatically generated by the kubernetes-nmstate release process.

/kind operator
/area provider/kubernetes

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[github-actions]

Dockerfile or bundle.Dockerfile is added/changed. Note that for security reasons none of these files are going to be used when building bundle. Docker file will be generated and all label information is taken from annotations.yaml.

[github-actions]

Dockerfile or bundle.Dockerfile is added/changed. Note that for security reasons none of these files are going to be used when building bundle. Docker file will be generated and all label information is taken from annotations.yaml.

[github-actions]

Dear @mkowalski,
Some errors and/or warnings were found while doing the check of your operator (kubernetes-nmstate-operator/0.88.0) against the entire suite of validators for Operator Framework with Operator-SDK version v1.36.0 and the command $ operator-sdk bundle validate <bundle-path> --select-optional suite=operatorframework.

Errors (:bug:) must be fixed while warnings (:warning:) are informative, and fixing them might improve the quality of your solution.

Type	Message
⚠️	Value nmstate.io/v1beta1, Kind=NodeNetworkConfigurationEnactment: provided API should have an example annotation
⚠️	Value nmstate.io/v1beta1, Kind=NodeNetworkConfigurationPolicy: provided API should have an example annotation
⚠️	Value nmstate.io/v1beta1, Kind=NodeNetworkState: provided API should have an example annotation
⚠️	Value nmstate.io/v1beta1, Kind=NMState: provided API should have an example annotation
⚠️	Value : (kubernetes-nmstate-operator.v0.88.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.
⚠️	Value kubernetes-nmstate-operator.v0.88.0: this bundle is using APIs which were deprecated and removed in v1.25. More info: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25. Migrate the API(s) for poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.Permissions[0].Rules[1]"])
⚠️	Value kubernetes-nmstate-operator.v0.88.0: owned CRD "nmstates.nmstate.io" has an empty description
⚠️	Value kubernetes-nmstate-operator.v0.88.0: owned CRD "nodenetworkconfigurationenactments.nmstate.io" has an empty description
⚠️	Value kubernetes-nmstate-operator.v0.88.0: owned CRD "nodenetworkconfigurationpolicies.nmstate.io" has an empty description
⚠️	Value kubernetes-nmstate-operator.v0.88.0: owned CRD "nodenetworkstates.nmstate.io" has an empty description
⚠️	Value kubernetes-nmstate-operator.v0.88.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/

[github-actions]

Dockerfile or bundle.Dockerfile is added/changed. Note that for security reasons none of these files are going to be used when building bundle. Docker file will be generated and all label information is taken from annotations.yaml.

[github-actions]

Dear @mkowalski,
Some errors and/or warnings were found while doing the check of your operator (kubernetes-nmstate-operator/0.88.0) against the entire suite of validators for Operator Framework with Operator-SDK version v1.36.0 and the command $ operator-sdk bundle validate <bundle-path> --select-optional suite=operatorframework.

Errors (:bug:) must be fixed while warnings (:warning:) are informative, and fixing them might improve the quality of your solution.

Type	Message
⚠️	Value nmstate.io/v1beta1, Kind=NMState: provided API should have an example annotation
⚠️	Value nmstate.io/v1beta1, Kind=NodeNetworkConfigurationEnactment: provided API should have an example annotation
⚠️	Value nmstate.io/v1beta1, Kind=NodeNetworkConfigurationPolicy: provided API should have an example annotation
⚠️	Value nmstate.io/v1beta1, Kind=NodeNetworkState: provided API should have an example annotation
⚠️	Value : (kubernetes-nmstate-operator.v0.88.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.
⚠️	Value kubernetes-nmstate-operator.v0.88.0: this bundle is using APIs which were deprecated and removed in v1.25. More info: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25. Migrate the API(s) for poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.Permissions[0].Rules[1]"])
⚠️	Value kubernetes-nmstate-operator.v0.88.0: owned CRD "nmstates.nmstate.io" has an empty description
⚠️	Value kubernetes-nmstate-operator.v0.88.0: owned CRD "nodenetworkconfigurationenactments.nmstate.io" has an empty description
⚠️	Value kubernetes-nmstate-operator.v0.88.0: owned CRD "nodenetworkconfigurationpolicies.nmstate.io" has an empty description
⚠️	Value kubernetes-nmstate-operator.v0.88.0: owned CRD "nodenetworkstates.nmstate.io" has an empty description
⚠️	Value kubernetes-nmstate-operator.v0.88.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/

[github-actions]

Dear @mkowalski,
Some errors and/or warnings were found while doing the check of your operator (kubernetes-nmstate-operator/0.88.0) against the entire suite of validators for Operator Framework with Operator-SDK version v1.36.0 and the command $ operator-sdk bundle validate <bundle-path> --select-optional suite=operatorframework.

Errors (:bug:) must be fixed while warnings (:warning:) are informative, and fixing them might improve the quality of your solution.

Type	Message
⚠️	Value nmstate.io/v1beta1, Kind=NMState: provided API should have an example annotation
⚠️	Value nmstate.io/v1beta1, Kind=NodeNetworkConfigurationEnactment: provided API should have an example annotation
⚠️	Value nmstate.io/v1beta1, Kind=NodeNetworkConfigurationPolicy: provided API should have an example annotation
⚠️	Value nmstate.io/v1beta1, Kind=NodeNetworkState: provided API should have an example annotation
⚠️	Value : (kubernetes-nmstate-operator.v0.88.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.
⚠️	Value kubernetes-nmstate-operator.v0.88.0: this bundle is using APIs which were deprecated and removed in v1.25. More info: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25. Migrate the API(s) for poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.Permissions[0].Rules[1]"])
⚠️	Value kubernetes-nmstate-operator.v0.88.0: owned CRD "nmstates.nmstate.io" has an empty description
⚠️	Value kubernetes-nmstate-operator.v0.88.0: owned CRD "nodenetworkconfigurationenactments.nmstate.io" has an empty description
⚠️	Value kubernetes-nmstate-operator.v0.88.0: owned CRD "nodenetworkconfigurationpolicies.nmstate.io" has an empty description
⚠️	Value kubernetes-nmstate-operator.v0.88.0: owned CRD "nodenetworkstates.nmstate.io" has an empty description
⚠️	Value kubernetes-nmstate-operator.v0.88.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/

[github-actions]

Dockerfile or bundle.Dockerfile is added/changed. Note that for security reasons none of these files are going to be used when building bundle. Docker file will be generated and all label information is taken from annotations.yaml.

[github-actions]

Dear @mkowalski,
Some errors and/or warnings were found while doing the check of your operator (kubernetes-nmstate-operator/0.88.0) against the entire suite of validators for Operator Framework with Operator-SDK version v1.36.0 and the command $ operator-sdk bundle validate <bundle-path> --select-optional suite=operatorframework.

Errors (:bug:) must be fixed while warnings (:warning:) are informative, and fixing them might improve the quality of your solution.

Type	Message
⚠️	Value nmstate.io/v1beta1, Kind=NMState: provided API should have an example annotation
⚠️	Value nmstate.io/v1beta1, Kind=NodeNetworkConfigurationEnactment: provided API should have an example annotation
⚠️	Value nmstate.io/v1beta1, Kind=NodeNetworkConfigurationPolicy: provided API should have an example annotation
⚠️	Value nmstate.io/v1beta1, Kind=NodeNetworkState: provided API should have an example annotation
⚠️	Value : (kubernetes-nmstate-operator.v0.88.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.
⚠️	Value kubernetes-nmstate-operator.v0.88.0: this bundle is using APIs which were deprecated and removed in v1.25. More info: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25. Migrate the API(s) for poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.Permissions[0].Rules[1]"])
⚠️	Value kubernetes-nmstate-operator.v0.88.0: owned CRD "nmstates.nmstate.io" has an empty description
⚠️	Value kubernetes-nmstate-operator.v0.88.0: owned CRD "nodenetworkconfigurationenactments.nmstate.io" has an empty description
⚠️	Value kubernetes-nmstate-operator.v0.88.0: owned CRD "nodenetworkconfigurationpolicies.nmstate.io" has an empty description
⚠️	Value kubernetes-nmstate-operator.v0.88.0: owned CRD "nodenetworkstates.nmstate.io" has an empty description
⚠️	Value kubernetes-nmstate-operator.v0.88.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/