v1.2.6 Armory Operator
2021/05/07 Release Notes
Armory scans the codebase as we develop and release software. For information about CVE scans for this release, contact your Armory account representative.
Google Cloud Storage (GCS) config missing
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
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
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 Enterprise 2.25.0 or higher. For more information, see Docker Artifacts.
- chore(release): upgrade to oss operator 1.2.5
Was this page helpful?
Thank you for letting us know!
Sorry to hear that. Please tell us how we can improve.
Last modified December 10, 2021: (556c295d)