Skip to content
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

build: Add release-ng-arm64-fips release target #46930

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

camscale
Copy link
Contributor

Add a release target to build.assets/Makefile to build the arm64-fips
release. This was missed before because I erroneously assumed we stopped
doing that due to rust build issues, but it was just that rdpclient was
no longer part of the arm64-fips build, not that we abandoned that build
altogether.

Add a release target to `build.assets/Makefile` to build the arm64-fips
release. This was missed before because I erroneously assumed we stopped
doing that due to rust build issues, but it was just that rdpclient was
no longer part of the arm64-fips build, not that we abandoned that build
altogether.
@camscale camscale added the no-changelog Indicates that a PR does not require a changelog entry label Sep 26, 2024
@rohithrrao
Copy link

@camscale looks like this just waiting for additional approvals. If you get got those, we would appreciate having FIPs compliant ARM64 docker images.

@camscale
Copy link
Contributor Author

@camscale looks like this just waiting for additional approvals. If you get got those, we would appreciate having FIPs compliant ARM64 docker images.

@rohithrrao This PR is for a new build method that is not yet in use. We already publish ARM64 fips images -public.ecr.aws/gravitational/teleport-ent-fips-distroless:16.4.3 was just published today and it contains AMD64 and ARM64 architectures.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-changelog Indicates that a PR does not require a changelog entry size/sm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants