-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: identity flavors #194
Conversation
…lity test, remove vlaidation breaking single capability test
FYSA: This is failing ci because of a zarf bug zarf-dev/zarf#2320, which is impacting main due to a change (change metrics server from |
Okay this should be good again. @jeff-mccoy not sure what you want to do with the keycloak specific interface/endpoint checks. Definitely nice to have on the full runs, but without istio they break the single package tests. I left them commented out for now just so ci would pass rather than deleting in case there were specific thoughts on keeping them in some capacity. |
Of course the full install failed immediately after i commented on the pepr jest tests, but dont think that is related to anything i implemented here. |
## Description Broke out flavored values files Created common keycloak component imported into flavored components Added templating for security context for keycloak image to facilitate using registry1 image Added templating to all helm resources that require istio to enable single capability tests to work Commented out keycloak validate task that checks the exposed endpoints as single capability tests dont have istio and cannot test that functionality Note: if using colima on a mac the local image in keycloak doesnt "just work" as crane requires the default docker sock unix:///var/run/docker.sock or DOCKER_HOST to be set. This behavior is unique to this scenario and colima does not symlink anymore so docker desktop can be colocated on the same machine. This can be resolved by running `export DOCKER_HOST=unix:///Users/<username>/.colima/<colima-profile>/docker.sock` prior to attempting to build the package containing keycloak. Tested on registry1 flavor on ubuntu amd64 and upstream with darwin arm64. ## Related Issue Fixes # <!-- or --> Relates to # ## Type of change - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Other (security config, docs update, etc) ## Checklist before merging - [x] Test, docs, adr added or updated as needed - [ ] [Contributor Guide Steps](https://github.com/defenseunicorns/uds-template-capability/blob/main/CONTRIBUTING.md)(https://github.com/defenseunicorns/uds-template-capability/blob/main/CONTRIBUTING.md#submitting-a-pull-request) followed --------- Co-authored-by: Micah Nagel <micah.nagel@defenseunicorns.com> Co-authored-by: Megamind <882485+jeff-mccoy@users.noreply.github.com>
Description
Broke out flavored values files
Created common keycloak component imported into flavored components
Added templating for security context for keycloak image to facilitate using registry1 image
Added templating to all helm resources that require istio to enable single capability tests to work
Commented out keycloak validate task that checks the exposed endpoints as single capability tests dont have istio and cannot test that functionality
Note: if using colima on a mac the local image in keycloak doesnt "just work" as crane requires the default docker sock unix:///var/run/docker.sock or DOCKER_HOST to be set. This behavior is unique to this scenario and colima does not symlink anymore so docker desktop can be colocated on the same machine. This can be resolved by running
export DOCKER_HOST=unix:///Users/<username>/.colima/<colima-profile>/docker.sock
prior to attempting to build the package containing keycloak.Tested on registry1 flavor on ubuntu amd64 and upstream with darwin arm64.
Related Issue
Fixes #
Relates to #
Type of change
Checklist before merging