Armory Docs – Armory Operator Release Notes

Continuous-Deployment: v1.8.5 Armory Operator

Thu, 11 May 2023 00:00:00 +0000

2023-05-11 Release Notes

Upgrade the Operator using kubectl replace. See Upgrade the Operator for details.

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known issues

Internal error: failed calling webhook when deploying Armory Continuous Deployment after upgrading the Armory Operator

After running the following command: kubectl -n armory apply -k overlays/dev/, admins see the following exception:

Error from server (InternalError): error when creating "overlays/dev/": Internal error occurred: failed calling webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io": Post "https://spinnaker-operator.armory.svc:443/validate-spinnaker-armory-io-v1alpha2-spinnakerservice?timeout=10s": context deadline exceeded

Or an exception like this:

Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io": Post "https://spinnaker-operator.armory-operator.svc:443/validate-spinnaker-armory-io-v1alpha2-spinnakerservice?timeout=10s": no endpoints available for service "spinnaker-operator"

To resolve this issue, customers should refer to KB article KB0010638.

Affected versions: 1.7.3+

Highlighted updates

Updates the Alpine version of the Operator image to Alpine 3.17

Armory Operator

chore(docker): update Alpine version to 3.17

Continuous-Deployment: v1.8.6 Armory Operator

Thu, 11 May 2023 00:00:00 +0000

2023-05-11 Release Notes

Upgrade the Operator using kubectl replace. See Upgrade the Operator for details.

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known issues

Internal error: failed calling webhook when deploying Armory Continuous Deployment after upgrading the Armory Operator

After running the following command: kubectl -n armory apply -k overlays/dev/, admins see the following exception:

Error from server (InternalError): error when creating "overlays/dev/": Internal error occurred: failed calling webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io": Post "https://spinnaker-operator.armory.svc:443/validate-spinnaker-armory-io-v1alpha2-spinnakerservice?timeout=10s": context deadline exceeded

Or an exception like this:

Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io": Post "https://spinnaker-operator.armory-operator.svc:443/validate-spinnaker-armory-io-v1alpha2-spinnakerservice?timeout=10s": no endpoints available for service "spinnaker-operator"

To resolve this issue, customers should refer to KB article KB0010638.

Affected versions: 1.7.3+

Highlighted updates

Updates the Alpine version of the Halyard image to Alpine 3.17

Armory Operator

chore(dependency): update upstream Halyard version

Continuous-Deployment: v1.8.8 Armory Operator

Thu, 11 May 2023 00:00:00 +0000

2023-11-08 Release Notes

Upgrade the Operator using kubectl replace. See Upgrade the Operator for details.

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known issues

Internal error: failed calling webhook when deploying Armory Continuous Deployment after upgrading the Armory Operator

After running the following command: kubectl -n armory apply -k overlays/dev/, admins see the following exception:

Error from server (InternalError): error when creating "overlays/dev/": Internal error occurred: failed calling webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io": Post "https://spinnaker-operator.armory.svc:443/validate-spinnaker-armory-io-v1alpha2-spinnakerservice?timeout=10s": context deadline exceeded

Or an exception like this:

Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io": Post "https://spinnaker-operator.armory-operator.svc:443/validate-spinnaker-armory-io-v1alpha2-spinnakerservice?timeout=10s": no endpoints available for service "spinnaker-operator"

To resolve this issue, customers should refer to KB article KB0010638.

Affected versions: 1.7.3+

Highlighted updates

Removed CVE-2022-22965 by upgrading org.springframework:spring-core, org.springframework:spring-beans and org.springframework:spring-webmv to the version 5.3.18

Armory Operator

chore(dependencies): updated operator armory-halyard version to 1.12.0-2c14811-operator

Continuous-Deployment: v1.3.1 Operator for Spinnaker

Tue, 09 May 2023 00:00:00 +0000

2023/05/09 Release Notes

Upgrade the Operator using kubectl replace. See Upgrade the Operator for details.

Security

Armory scans the codebase before releasing software. Contact your Armory representative for information about CVE scans for this release.

Known Issues

No known issues.

Highlighted updates

This release updates the Alpine base image version of the Spinnaker Operator and Halyard images to 3.17.

The following table outlines compatible versions of Kubernetes, the Armory Operator, Armory CD, the Spinnaker Operator, and Spinnaker:

Kubernetes Version	Armory Operator Version	Armory CD Version
< 1.21	<= 1.6.x	<= 2.28.0
>= 1.21	>= 1.7.x	All supported versions

</div>
<div class="tab-body tab-pane fade"
id="tabs-00-01" role="tabpanel" aria-labelled-by="tabs-00-01-tab" tabindex="0">
<table>

Kubernetes Version Spinnaker Operator Version Spinnaker Version < 1.21 <= 1.2.5 >= 1.27.3 >= 1.21 >= 1.3.x >= 1.27.3

</div>

Consult the Manage Operator guide for how to upgrade your Operator version.

Armory recommends upgrading your Operator installation before upgrading your Kubernetes cluster beyond 1.21. There are no other expected migration steps for this upgrade.

Spinnaker Operator

chore(docker): update alpine images operator + halyard (#292) (#293)

Continuous-Deployment: v1.4.0 Operator for Spinnaker

Tue, 09 May 2023 00:00:00 +0000

2023/05/09 Release Notes

Upgrade the Operator using kubectl replace. See Upgrade the Operator for details.

Security

Armory scans the codebase before releasing software. Contact your Armory representative for information about CVE scans for this release.

Known Issues

No known issues.

Highlighted updates

This release adds support for the GA Ingress controller, which is needed when deploying Spinnaker Operator into versions of Kubernetes >= 1.22. Additionally, the release updates the Alpine base image version of the Spinnaker Operator and Halyard images to 3.17.

The following table outlines compatible versions of Kubernetes, the Armory Operator, Armory CD, the Spinnaker Operator, and Spinnaker:

Kubernetes Version	Armory Operator Version	Armory CD Version
< 1.21	<= 1.6.x	<= 2.28.0
>= 1.21	>= 1.7.x	All supported versions

</div>
<div class="tab-body tab-pane fade"
id="tabs-00-01" role="tabpanel" aria-labelled-by="tabs-00-01-tab" tabindex="0">
<table>

Kubernetes Version Spinnaker Operator Version Spinnaker Version < 1.21 <= 1.2.5 >= 1.27.3 >= 1.21 >= 1.3.x >= 1.27.3

</div>

Consult the Manage Operator guide for how to upgrade your Operator version.

Armory recommends upgrading your Operator installation before upgrading your Kubernetes cluster beyond 1.21. There are no other expected migration steps for this upgrade.

Spinnaker Operator

feat(k8s): add support for GA ingress apiVersion in helm chart and operator
chore(docker): update alpine images operator + halyard (#292) (#293)

Continuous-Deployment: v1.3.0 Operator for Spinnaker

Wed, 22 Feb 2023 00:00:00 +0000

2023/02/22 Release Notes

Upgrade the Operator using kubectl replace. See Upgrade the Operator for details.

Security

Armory scans the codebase before releasing software. Contact your Armory representative for information about CVE scans for this release.

Known Issues

No known issues.

Highlighted updates

This release introduces support for Kubernetes versions 1.22 and newer.

The following table outlines compatible versions of Kubernetes, the Armory Operator, Armory CD, the Spinnaker Operator, and Spinnaker:

Kubernetes Version	Armory Operator Version	Armory CD Version
< 1.21	<= 1.6.x	<= 2.28.0
>= 1.21	>= 1.7.x	All supported versions

</div>
<div class="tab-body tab-pane fade"
id="tabs-00-01" role="tabpanel" aria-labelled-by="tabs-00-01-tab" tabindex="0">
<table>

Kubernetes Version Spinnaker Operator Version Spinnaker Version < 1.21 <= 1.2.5 >= 1.27.3 >= 1.21 >= 1.3.x >= 1.27.3

</div>

Consult the Manage Operator guide for how to upgrade your Operator version.

Armory recommends upgrading your Operator installation before upgrading your Kubernetes cluster beyond 1.21. There are no other expected migration steps for this upgrade.

Spinnaker Operator

chore(dependency): update upstream open source Halyard version.
fix(build): kind unable to start control-plane
chore(build): make sure forks can run tests, but not create releases
fix(xform): transforming k8s secrets
feat(operator): update files for the new API of k8s v1.22
feat(lambda/validation): Validation regarding the AWS Lambda using the GO SDK to get the Lambda Functions using the AWS provider credentials

Continuous-Deployment: v1.8.3 Armory Operator

Mon, 23 Jan 2023 00:00:00 +0000

2023-01-23 Release Notes

Upgrade the Operator using kubectl replace. See Upgrade the Operator for details.

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known issues

Armory Operator may fail to start in some EKS clusters. Please upgrade to Armory Operator v1.8.4.

Internal error: failed calling webhook when deploying Armory Continuous Deployment after upgrading the Armory Operator

After running the following command: kubectl -n armory apply -k overlays/dev/, admins see the following exception:

Error from server (InternalError): error when creating "overlays/dev/": Internal error occurred: failed calling webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io": Post "https://spinnaker-operator.armory.svc:443/validate-spinnaker-armory-io-v1alpha2-spinnakerservice?timeout=10s": context deadline exceeded

Or an exception like this:

Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io": Post "https://spinnaker-operator.armory-operator.svc:443/validate-spinnaker-armory-io-v1alpha2-spinnakerservice?timeout=10s": no endpoints available for service "spinnaker-operator"

To resolve this issue, customers should refer to KB article KB0010638.

Affected versions: 1.7.3+

Highlighted updates

Helm chart support for basic-mode installation pattern

Armory Operator

chore(helm): Add support for namespace-scoped RBAC.

Continuous-Deployment: v1.8.4 Armory Operator

Mon, 23 Jan 2023 00:00:00 +0000

2023-01-23 Release Notes

Upgrade the Operator using kubectl replace. See Upgrade the Operator for details.

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known issues

Internal error: failed calling webhook when deploying Armory Continuous Deployment after upgrading the Armory Operator

After running the following command: kubectl -n armory apply -k overlays/dev/, admins see the following exception:

Error from server (InternalError): error when creating "overlays/dev/": Internal error occurred: failed calling webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io": Post "https://spinnaker-operator.armory.svc:443/validate-spinnaker-armory-io-v1alpha2-spinnakerservice?timeout=10s": context deadline exceeded

Or an exception like this:

Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io": Post "https://spinnaker-operator.armory-operator.svc:443/validate-spinnaker-armory-io-v1alpha2-spinnakerservice?timeout=10s": no endpoints available for service "spinnaker-operator"

To resolve this issue, customers should refer to KB article KB0010638.

Affected versions: 1.7.3+

Highlighted updates

Resolves the issue that prevented Armory Operator from starting in some EKS clusters.

Armory Operator

chore(dependency): update upstream Halyard version

Continuous-Deployment: v1.8.0 Armory Operator

Mon, 19 Dec 2022 00:00:00 +0000

2022-12-19 Release Notes

Upgrade the Operator using kubectl replace. See Upgrade the Operator for details.

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known issues

Internal error: failed calling webhook when deploying Armory Continuous Deployment after upgrading the Armory Operator

After running the following command: kubectl -n armory apply -k overlays/dev/, admins see the following exception:

Error from server (InternalError): error when creating "overlays/dev/": Internal error occurred: failed calling webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io": Post "https://spinnaker-operator.armory.svc:443/validate-spinnaker-armory-io-v1alpha2-spinnakerservice?timeout=10s": context deadline exceeded

Or an exception like this:

Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io": Post "https://spinnaker-operator.armory-operator.svc:443/validate-spinnaker-armory-io-v1alpha2-spinnakerservice?timeout=10s": no endpoints available for service "spinnaker-operator"

To resolve this issue, customers should refer to KB article KB0010638.

Affected versions: 1.7.3+

Highlighted updates

Config Maps as a data source

kind: ConfigMap
metadata:
 name: halyard-config-map
data:
 config: |
 halyard:
 configSourceType: secret # or configMap

Support for using a different Regex engine when structuring ignore patterns – enabling this feature flag allows for negative lookahead
```
spec:
 spinnakerConfig:
 config:
 armory:
 dinghy:
 enabled: true
 dinghyIgnoreRegexp2Enabled: true
```
See Negative expressions support in your dinghyfile for more information.

Armory Operator

chore(secrets): Add SecretOrConfigMapData type
feat(secrets): Add the secrets extracting from ConfigMap
chore(halyard): bump Halyard, add dinghyIgnoreRegexp2Enabled feature

Continuous-Deployment: v1.8.1 Armory Operator

Mon, 19 Dec 2022 00:00:00 +0000

2022-12-19 Release Notes

Upgrade the Operator using kubectl replace. See Upgrade the Operator for details.

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known issues

Internal error: failed calling webhook when deploying Armory Continuous Deployment after upgrading the Armory Operator

After running the following command: kubectl -n armory apply -k overlays/dev/, admins see the following exception:

Error from server (InternalError): error when creating "overlays/dev/": Internal error occurred: failed calling webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io": Post "https://spinnaker-operator.armory.svc:443/validate-spinnaker-armory-io-v1alpha2-spinnakerservice?timeout=10s": context deadline exceeded

Or an exception like this:

Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io": Post "https://spinnaker-operator.armory-operator.svc:443/validate-spinnaker-armory-io-v1alpha2-spinnakerservice?timeout=10s": no endpoints available for service "spinnaker-operator"

To resolve this issue, customers should refer to KB article KB0010638.

Affected versions: 1.7.3+

Highlighted updates

Operator now supports disabling the Admission Controller.

Armory Operator

fix(helm): Adding disable-admission-controller option to Helm chart

Continuous-Deployment: v1.8.2 Armory Operator

Mon, 19 Dec 2022 00:00:00 +0000

2022-12-19 Release Notes

Upgrade the Operator using kubectl replace. See Upgrade the Operator for details.

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known issues

Internal error: failed calling webhook when deploying Armory Continuous Deployment after upgrading the Armory Operator

After running the following command: kubectl -n armory apply -k overlays/dev/, admins see the following exception:

Error from server (InternalError): error when creating "overlays/dev/": Internal error occurred: failed calling webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io": Post "https://spinnaker-operator.armory.svc:443/validate-spinnaker-armory-io-v1alpha2-spinnakerservice?timeout=10s": context deadline exceeded

Or an exception like this:

Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io": Post "https://spinnaker-operator.armory-operator.svc:443/validate-spinnaker-armory-io-v1alpha2-spinnakerservice?timeout=10s": no endpoints available for service "spinnaker-operator"

To resolve this issue, customers should refer to KB article KB0010638.

Affected versions: 1.7.3+

Highlighted updates

This release resolves CVE GHSA-599f-7c49-w659.

Armory Operator

fix(cve): Upgrade Armory Halyard version

Continuous-Deployment: v1.7.3 Armory Operator

Tue, 18 Oct 2022 00:00:00 +0000

2022-10-18 Release Notes

Upgrade the Operator using kubectl replace. See Upgrade the Operator for details.

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known issues

Internal error: failed calling webhook when deploying Armory Continuous Deployment after upgrading the Armory Operator

After running the following command: kubectl -n armory apply -k overlays/dev/, admins see the following exception:

Error from server (InternalError): error when creating "overlays/dev/": Internal error occurred: failed calling webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io": Post "https://spinnaker-operator.armory.svc:443/validate-spinnaker-armory-io-v1alpha2-spinnakerservice?timeout=10s": context deadline exceeded

Or an exception like this:

Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io": Post "https://spinnaker-operator.armory-operator.svc:443/validate-spinnaker-armory-io-v1alpha2-spinnakerservice?timeout=10s": no endpoints available for service "spinnaker-operator"

To resolve this issue, customers should refer to KB article KB0010638.

Affected versions: 1.7.3+

Highlighted updates

Support for using a different Regex engine when structuring ignore patterns – enabling this feature flag allows for negative lookahead
```
spec:
 spinnakerConfig:
 config:
 armory:
 dinghy:
 enabled: true
 dinghyIgnoreRegexp2Enabled: true
```
See Negative expressions support in your dinghyfile for more information.

Armory Operator

chore(halyard): bump Halyard, add dinghyIgnoreRegexp2Enabled feature

Continuous-Deployment: v1.7.0 Armory Operator

Mon, 16 May 2022 00:00:00 +0000

2022/05/16 Release Notes

Upgrade the Operator using kubectl replace. See Upgrade the Operator for details.

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known issues

No known issues.

Highlighted updates

Operator now supports Kubernetes versions greater than 1.21. The following table outlines compatible versions of Operator, Kubernetes, and Armory Enterprise:

Kubernetes Version	Armory Operator Version	Armory CD Version
< 1.21	<= 1.6.x	<= 2.28.0
>= 1.21	>= 1.7.x	All supported versions

Kubernetes Version	Spinnaker Operator Version	Spinnaker Version
< 1.21	<= 1.2.5	>= 1.27.3
>= 1.21	>= 1.3.x	>= 1.27.3

Consult the Manage Operator guide for how to upgrade your Operator version.

Armory Operator

feat(core): upgrade to operator-sdk 0.18

Continuous-Deployment: v1.6.0 Armory Operator

Wed, 26 Jan 2022 00:00:00 +0000

2022/01/26 Release Notes

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known issues

No known issues.

Highlighted updates

Operator now supports the following configuration options for sidecars: resources,readinessProbe, and startupProbe.

Armory Operator

feat(sidecars): Support resources and startup|readiness probes

Continuous-Deployment: v1.5.1 Armory Operator

Tue, 21 Dec 2021 00:00:00 +0000

2021/12/21 Release Notes

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known issues

No known issues.

Highlighted updates

This release fixes the canary validator issue that caused the Armory Continuous Deployment deployment to fail when metadataCachingIntervalMS was in the canary configuration.

In addition to the fix, new functionality has been added that enables users to disable the canary validators by adding spec.validation.providers.canary: false to the Operator configuration.

Armory Operator

fix(canary/validator): Errors on MetadataCachingIntervalMS
fix(canary/validator): Enable or disable canary validation

Continuous-Deployment: v1.4.1 Armory Operator

Sat, 24 Jul 2021 00:00:00 +0000

2021/07/24 Release Notes

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known issues

Canary validation

When canary validators are enabled and users add metadataCachingIntervalMS to the canary configuration, deployment fails with the following error message in the Operator logs:

json: cannot unmarshal number into Go struct field PrometheusCanaryServiceIntegration.metadataCachingIntervalMS of type bool

Workaround

None.

Affected versions: Armory Operator 1.4.0, 1.4.1

Fixed versions: Armory Operator 1.5.1

Highlighted updates

This release updated two of the libraries that the Operator uses:

krb5-libs to 1.18.4-r0
Halyard to 1.12.0-0422a50-operator

Armory Operator

chore(halyard): update halyard-version
chore(halyard): fix krb5-libs version

Continuous-Deployment: v1.4.0 Armory Operator

Wed, 21 Jul 2021 00:00:00 +0000

2021/07/21 Release Notes

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known issues

Canary validation

When canary validators are enabled and users add metadataCachingIntervalMS to the canary configuration, deployment fails with the following error message in the Operator logs:

json: cannot unmarshal number into Go struct field PrometheusCanaryServiceIntegration.metadataCachingIntervalMS of type bool

Workaround

None.

Affected versions: Armory Operator 1.4.0, 1.4.1

Fixed versions: Armory Operator 1.5.1

Highlighted updates

New `registrationId` label for SpinnakerService status

This release adds the new registrationId label, used for identifying your Armory Continuous Deployment cluster, under the status section on the spinnakerservices.spinnaker.armory.io CRD. You need to install the latest CRD in order to see this feature working.

Execute kubectl -n spinnaker get spinsvc to see the new label after you have installed the latest CRD.

Armory Operator

feat(validators): add prometheus canary validator
feat(validators): add aws canary validator
feat(validator): add clouddriver ha validation
feat(registration-id): add registration id

Continuous-Deployment: v1.2.7 Armory Operator

Wed, 19 May 2021 00:00:00 +0000

2021/05/19 Release Notes

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known issues

No known issues.

Fixed issues

The GCS bucketLocation issue introduced in 1.2.6 has been fixed.

Armory Operator

chore(cve): resolves CVEs: CVE-2020-14343, CVE-2020-25658
chore(halyard) update halyard version

Continuous-Deployment: v1.2.5 Operator for Spinnaker

Fri, 07 May 2021 00:00:00 +0000

2021/05/07 Release Notes

Upgrade the Operator using kubectl replace. See Upgrade the Operator for details.

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known Issues

No known issues.

Highlighted updates

Docker artifacts

This release adds support for the repositoriesRegex field. Use the field to provide regex that specifies what repositories Clouddriver caches images from. This is useful if you add repos frequently. Any new repo that matches the regex gets cached automatically.

This feature requires Armory Continuous Deployment 2.25.0 or higher. For more information, see Docker Artifacts.

Spinnaker Operator

feat(validation): Add a CloudFoundry validation.
chore(halyard): Update halyard version.

Continuous-Deployment: v1.2.6 Armory Operator

Fri, 07 May 2021 00:00:00 +0000

2021/05/07 Release Notes

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known issues

Google Cloud Storage (GCS) config missing `bucketLocation` fails

If you have configured a persistent storage or a canary service integration account for GCS without the bucketLocation property defined, validation fails with a message similar to this:

Failed to ensure the required bucket "mybucket" exists: bucketLocation, spinnakerConfig.config.default.canary: Failed to ensure the required bucket "mybucket" exists: bucketLocation, spinnakerConfig.config.default.canary.google.gcp-canary: Failed to ensure the required bucket "mybucket" exists: bucketLocation

Workaround

If you don’t have a bucket location, you should configure bucketLocation as a blank string. See the bucketLocation key in the following example:

persistentStorage:
 gcs:
 bucket: <your-bucket-name>
 bucketLocation: "" # use an emptry string if you don't have a bucket location
 jsonPath: <path-to-encrypted-json-file>
 project: <your-cloud-project>
 rootFolder: front50
 persistentStoreType: gcs

Affected versions: Halyard 1.12.0, Armory Operator 1.2.6

Fixed versions: Halyard 1.12.01, Armory Operator 1.2.7

Highlighted updates

Docker artifacts

This feature requires Armory Continuous Deployment 2.25.0 or higher. For more information, see Docker Artifacts.

Armory Operator

chore(release): upgrade to oss operator 1.2.5

Continuous-Deployment: v1.2.4 Operator for Spinnaker

Wed, 17 Mar 2021 00:00:00 +0000

03/17/2021 Release Notes

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known Issues

No known issues.

Spinnaker Operator

feat(health-check): increase timeout and validate ready replicas for SpinnakerService status

Continuous-Deployment: v1.2.5 Armory Operator

Wed, 17 Mar 2021 00:00:00 +0000

03/17/2021 Release Notes

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known Issues

No known issues.

Armory Operator

chore(release): upgrade to oss operator 1.2.4

Continuous-Deployment: v1.2.3 Armory Operator

Mon, 01 Mar 2021 00:00:00 +0000

03/01/2021 Release Notes

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known Issues

No known issues.

Armory Operator

feat(docker): adding ecr utility to get an ecr token

Continuous-Deployment: v1.2.3 Operator for Spinnaker

Mon, 01 Mar 2021 00:00:00 +0000

03/01/2021 Release Notes

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known Issues

No known issues.

Operator for Spinnaker

fix(timeout): avoid revalidation when patching status
chore(cve): fix for CVE-2020-13757
feat(validator/aws): add aws account validator
fix(validation): validate primary account for kubernetes provider
fix(expose): override public service port
chore(halyard): Updated halyard version

Continuous-Deployment: v1.2.4 Armory Operator

Mon, 01 Mar 2021 00:00:00 +0000

03/01/2021 Release Notes

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known Issues

No known issues.

Armory Operator

chore(release): upgrade to oss operator 1.2.3

Continuous-Deployment: v1.3.0 Armory Operator

Mon, 01 Mar 2021 00:00:00 +0000

2021/06/30 Release Notes

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known issues

No known issues.

Breaking changes

Spinnaker Accounts CRD

The spinnakeraccounts.spinnaker.io CRD is no longer supported in this release. Now you need to install armoryaccounts.spinnaker.armory.io CRD and rename your existing accounts.

Highlighted updates

Support Diagnostics

This release adds support for the Support Diagnostics service for Armory Continuous Deployment.

This feature requires you to have diagnostics enabled within your SpinnakerService. For more information, see Configure Support Diagnostics for Armory Continuous Deployment.

Armory Operator

feat(debug): send debug information when reconcile spinsvc

Continuous-Deployment: v1.2.2 Armory Operator

Wed, 02 Dec 2020 00:00:00 +0000

12/02/2020 Release Notes

Security

Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.

Known Issues

No known issues.

Armory Operator

chore(cve): resolves CVEs: CVE-2020-28928 CVE-2020-28196
chore(halyard) update halyard version

Spinnaker Operator

chore(halyard): Updated halyard version

Continuous-Deployment: v1.2.1 Armory Operator

Mon, 16 Nov 2020 00:00:00 +0000

11/16/2020 Release Notes

Known Issues

No known issues.

Armory Operator

chore(cve): fix for CVE-2020-13757
chore(halyard) update oss version
chore(release): upgrade to oss operator 1.2.1

Spinnaker Operator

fix(timeout): avoid revalidation when patching Spinnaker Status.
chore(cve): fix for CVE-2020-13757
feat(validator/aws): add aws account validator.
chore(halyard): Updated halyard version

Continuous-Deployment: v1.2.0 Armory Operator

Wed, 07 Oct 2020 00:00:00 +0000

10/07/2020 Release Notes

Known Issues

No known issues.

Armory Operator

chore(release): upgrade to oss operator 1.2.0
chore(halyard): Update halyard version.

Spinnaker Operator

chore(halyard): Update halyard version.

Continuous-Deployment: v1.1.2 Armory Operator

Wed, 30 Sep 2020 00:00:00 +0000

09/30/2020 Release Notes

Known Issues

No known issues.

Armory Operator

chore(release): upgrade to oss operator 1.1.2
chore(license): update LICENSES
fix(helm): solve error assigning version to Helm Chart
feat(ubi): add build for ubi images

Spinnaker Operator

fix(ingress): Support ingress with load balancer IP (GCE/bare metal)
chore(halyard): Update halyard version.
fix(validation): Validation Kubernetes accounts using the context passed on Spinnaker Service.
refactor(status): Introducing a better way to check spinnaker health validating correct status of each pod.

Continuous-Deployment: v1.1.1 Armory Operator

Thu, 13 Aug 2020 00:00:00 +0000

08/13/2020 Release Notes

Known Issues

No known issues.

Armory Operator

fix(expose/ingress): added integration test for ingress
fix(expose/ingress): added ingress permissions to role manifests.
chore(release): upgrade to oss operator 1.1.1

Spinnaker Operator

fix(test): Added ingress permissions to role used in tests
fix(expose/ingress): solve issue for spinsvc status URL

Continuous-Deployment: v1.1.0 Armory Operator

Tue, 11 Aug 2020 00:00:00 +0000

08/11/2020 Release Notes

Known Issues

This release does not include updated permissions for the Operator to manage Ingress objects. You can add the following to the role that is created for the operator in your cluster:

- apiGroups:
 - networking.k8s.io
 - extensions
 resources:
 - ingresses
 verbs:
 - get
 - list
 - watch

This will be addressed in a patch release for the 1.1.x release line.

Highlights

Ingress Support

spec.expose.type: ingress. When ingress is selected, the Operator tries to find an ingress rule in the same namespace as Spinnaker that points to Gate or Deck. It will then compute these services’ hostnames using either spec.rules[].host or status.loadBalancer.ingress[0].hostname.

Both extensions and networking.k8s.io ingresses are supported and queried.

For Gate, the Operator also checks for the path and sets up Spinnaker to support relative paths.

The following example sets up Spinnaker’s UI (Deck) at http://acme.com and API (Gate) at http://acme.com/api:

kind: Ingress
apiVersion: extensions/v1beta1
metadata:
 name: my-ingress
 namespace: spinnaker
spec:
 rules:
 - http:
 paths:
 - path: /api
 backend:
 serviceName: spin-gate
 servicePort: http
 - path: /
 backend:
 serviceName: spin-deck
 servicePort: 9000
status:
 loadBalancer:
 ingress:
 - hostname: acme.com

This example sets up the UI (Deck) at https://acme.com and API (Gate) at https://acme.com/api/v1:

kind: Ingress
apiVersion: networking.k8s.io/v1beta1
metadata:
 name: my-ingress
 namespace: spinnaker
spec:
 tls:
 - hosts: [ 'example.com', 'acme.com'] # That's how we know TLS is supported
 rules:
 - host: acme.com
 http:
 paths:
 - path: /api
 backend:
 serviceName: spin-gate
 servicePort: http
 - path: /
 backend:
 serviceName: spin-deck
 servicePort: 9000

Detailed updates

Armory Operator

chore(release): upgrade to oss operator 1.1.0
chore(vault): Error messages not capitalized
fix(kustomize): Make kustomization.yml more compatible so that it works with kubectl and kustomize
feat(vault): Mount vault’s self-signed CA into services

Spinnaker Operator

fix(validation): name ports in generated service, declare container ports in manifest
fix(accounts): Add Spring profile on specialized services
feat(expose/ingress): ingress support, name all ports on services, fix config clone
fix(validation): Issue patch to update status
fix(validation): Add parallel validation support; making kubectl apply calls much quicker
chore(release): Updated halyard version
fix(defaults): Use long delays instead of archaius.enabled: false to not break hystrix defaults
feat(settings): Global service-settings
fix(secrets): Prevent panic if a file in secret is empty
chore(errors): Better error messages validating kubeconfig files

Continuous-Deployment: v1.0.3 Armory Operator

Mon, 03 Aug 2020 00:00:00 +0000

08/03/2020 Release Notes

Known Issues

No known issues.

Armory Operator

Fixed a bug in FreeForm. It caused transformers that attempt to modify the config (or profiles) in memory to leak the change into the operator’s informer cache.
Validation webhooks now patch the status. Operator cannot return the patches directly because we’re changing the status. This resolves some validation errors when trying to apply a new SpinnakerService.
Validation service has ports named for Istio support
Fixed an issue that caused crashes when using SpinnakerAccount with sharded services (“HA mode”).
Made kustomization.yml more compatible.