SDK for building Kubernetes applications. Provides high level APIs, useful abstractions, and project scaffolding.
APACHE-2.0 License
Bot releases are visible (Hide)
Published by github-actions[bot] 2 months ago
No changes for this release!
Published by github-actions[bot] 4 months ago
Published by github-actions[bot] 5 months ago
No changes for this release!
Published by oceanc80 8 months ago
make install
: fix a bug where the command would silently fail if GOBIN wasn't set. (https://github.com/operator-framework/operator-sdk/pull/6629)Published by github-actions[bot] 10 months ago
--config
flag due to the controller-runtime ComponentConfig package being deprecated with the planned removal of support for loading manager options from a file. (#6613)operator-sdk olm install
: fix a bug where the retry logic would not retry until the the command's timeout was reached, resulting in early exiting of the command before the specified timeout was reached. (#6613)Published by github-actions[bot] about 1 year ago
--force
option. This behavior could have undesired side effects in some scenario.helm.sdk.operatorframework.io/rollback-force: false
Published by github-actions[bot] about 1 year ago
quay.io/operator-framework/ansible-operator
base image to now use Ansible 2.15.0. Removes pre-installed Python modules that are not required to build and run the testdata/ansible/memcached-operator
sample. Updates Python to 3.9 to work with Ansible 2.15.0. (#6483)ansible/v1
plugin scaffolding to: - Remove the community.kubernetes
collection - Update the operator_sdk.util
collection from v0.4.0
--> v0.5.0
- Update the molecule.yaml
files to work with molecule v5.1.0
. (#6483)quay.io/operator-framework/ansible-operator-2.11-preview
image. This image will no longer be built after Operator-SDK v1.30.0. (#6483)olm install
command is failed for "no-match" error.$ operator-sdk olm install --verbose ... FATA[0001] Failed to install OLM version "latest": failed to create CRDs and resources: no matches for kind "OLMConfig" in version "operators.coreos.com/v1"
. Now, in this case, operator-sdk tries to create the resource again, until it succeeds (or until the timeout exceeded). (#6490)run bundle
command does not copy all FBC manifests into the new catalog image if custom index-image is passed. (#6512)markUnsafe
now correctly marks as unsafe the all variables passed in spec
. (#6376)Published by github-actions[bot] over 1 year ago
overrideValues
in your watches.yaml
, every entry is logged with its key and its value. When working with confidential information such as credentials, logging those information would not be optimal nor desirable. Therefore, there should be a way to silence/suppress these values.--suppress-override-values
boolean-flag for the helm-operator
. When set to true, the value of the overrideValues entry is sanitized with this value "****".overrideValues
of the watches.yaml
```yaml overrideValues:The default-value of `--suppress-override-values` is `false` so therefore we would get this warning logged: `Chart value x overridden to y by operator's watches.yaml`
When setting `--suppress-override-values` `true` the warning will be logged in the following manner: `Chart value x overridden to **** by operator's watches.yaml`. ([#6469](https://github.com/operator-framework/operator-sdk/pull/6469))
- (images): Bumps all Operator SDK maintained images to now use ubi(-minimal) tag 8.8. ([#6466](https://github.com/operator-framework/operator-sdk/pull/6466))
### Bug Fixes
- In `run bundle-upgrade`, hash the cache directory name to avoid error of too long file name. ([#6477](https://github.com/operator-framework/operator-sdk/pull/6477))
Published by github-actions[bot] over 1 year ago
... ConfigMap ... is invalid: []: Too long: must have at most 1048576 bytes
.Published by github-actions[bot] over 1 year ago
No changes for this release!
Published by github-actions[bot] over 1 year ago
1.25
to 1.26
. - Upgrade sigs.k8s.io/controller-tools
from v0.10.0
to v0.11.3
. More info: https://github.com/kubernetes-sigs/controller-tools/releases - Upgrade sigs.k8s.io/controller-runtime
dependency from v0.13.0
to v0.14.5
. More info: https://github.com/kubernetes-sigs/controller-runtime/releases - Upgrade k8s.io/client-go
dependency from v0.25.3
to v0.26.2
. - Upgrade controller-gen
dependency from v0.10.0
to v0.11.1
. - Upgrade kube-rbac-proxy
from v0.13.0
to v0.13.1
- Modify gov4alpha plugin to use go/v4-alpha
from Kubebuilder. (#6352)--pod-security=restricted
. (#6335)Published by github-actions[bot] over 1 year ago
operator-sdk run bundle(-upgrade)
: Change default of the --security-context-config
flag to be legacy
instead of restricted
. (#6226)operator-sdk run bundle
: When creating the CatalogSource, we now set the grpcPodConfig.SecurityContextConfig
to the value of the --security-context-config
flag. (#6226)operator-sdk bundle validate
: Fix a bug in the Kubernetes 1.25 validation logic that would warn that a Kubernetes resource was deprecated without checking the group that contains the resource. (i.e if apps/deployments was deprecated and you used other/deployments you would recieve a warning)". The validation logic will now verify the group and resource before issuing a warning. (#6231)operator-sdk run bundle(-upgrade)
: Fix a bug where SQLite bundle images were failing to be run properly due to a change in the default channel that is used by run bundle(-upgrade)
when creating a subscription. (#6226)operator-sdk run bundle(-upgrade)
: Update the logic used to set a Registry Pod's PSA configuration to fix a bug where a Pod's containers still had a restrictive SecurityContext even when setting --security-context-config=legacy
. (#6226)Published by github-actions[bot] over 1 year ago
operator-sdk run bundle(-upgrade)
: Change default of the --security-context-config
flag to be legacy
instead of restricted
. (#6210)operator-sdk run bundle
: When creating the CatalogSource, we now set the grpcPodConfig.SecurityContextConfig
to the value of the --security-context-config
flag. (#6210)scorecard-test-kuttl
image always prints the kuttl logs in case there is an error processing the kuttl report. (#6225)operator-sdk bundle validate
: Fix a bug in the Kubernetes 1.25 validation logic that would warn that a Kubernetes resource was deprecated without checking the group that contains the resource. (i.e if apps/deployments was deprecated and you used other/deployments you would recieve a warning)". The validation logic will now verify the group and resource before issuing a warning. (#6227)operator-sdk run bundle(-upgrade)
: Fix a bug where SQLite bundle images were failing to be run properly due to a change in the default channel that is used by run bundle(-upgrade)
when creating a subscription. (#6210)operator-sdk run bundle(-upgrade)
: Update the logic used to set a Registry Pod's PSA configuration to fix a bug where a Pod's containers still had a restrictive SecurityContext even when setting --security-context-config=legacy
. (#6210)operator-sdk bundle validate
: Fix a bug that would make the command exit with a 0 exit code even if there were validation failures. (#6274).spec
field, which is a perfectly valid scenario. Instead of throwing an error scorecard will now issue a suggestion. (#6245)Published by github-actions[bot] over 1 year ago
operator-sdk run bundle(-upgrade)
: Change default of the --security-context-config
flag to be legacy
instead of restricted
. (#6261)operator-sdk run bundle
: When creating the CatalogSource, we now set the grpcPodConfig.SecurityContextConfig
to the value of the --security-context-config
flag. (#6261)operator-sdk bundle validate
: Fix a bug in the Kubernetes 1.25 validation logic that would warn that a Kubernetes resource was deprecated without checking the group that contains the resource. (i.e if apps/deployments was deprecated and you used other/deployments you would recieve a warning)". The validation logic will now verify the group and resource before issuing a warning. (#6263)operator-sdk run bundle(-upgrade)
: fix a bug in the logic that would attempt to create a ConfigMap
that contained the entire contents of an FBC. Now if the FBC contents are to large to fit into a single ConfigMap
, the FBC contents will be partitioned and split amongst multiple ConfigMap
resources. (#6262)operator-sdk run bundle(-upgrade)
: Fix a bug where SQLite bundle images were failing to be run properly due to a change in the default channel that is used by run bundle(-upgrade)
when creating a subscription. (#6261)operator-sdk run bundle(-upgrade)
: Update the logic used to set a Registry Pod's PSA configuration to fix a bug where a Pod's containers still had a restrictive SecurityContext even when setting --security-context-config=legacy
. (#6261).spec
field, which is a perfectly valid scenario. Instead of throwing an error scorecard will now issue a suggestion. (#6266)Published by github-actions[bot] almost 2 years ago
operator-sdk bundle validate
: When checking for Kubernetes APIs deprecated in Kubernetes v1.25.0 the ClusterServiceVersion's CustomResourceDefinitions, ClusterPermissions, and Permissions are now validated to ensure no references to deprecated APIs are being made. (#6119)operator-sdk run bundle(-upgrade)
: fix a bug in the logic that would attempt to create a ConfigMap
that contained the entire contents of an FBC. Now if the FBC contents are to large to fit into a single ConfigMap
, the FBC contents will be partitioned and split amongst multiple ConfigMap
resources. (#6182)