Skip to content

Comments

feat: add support for scheduling against kubernetes.azure.com/fips_enabled#1438

Open
matthchr wants to merge 4 commits intomainfrom
matthchr/fips-label
Open

feat: add support for scheduling against kubernetes.azure.com/fips_enabled#1438
matthchr wants to merge 4 commits intomainfrom
matthchr/fips-label

Conversation

@matthchr
Copy link
Member

@matthchr matthchr commented Feb 18, 2026

  • This adds the ability to simulate scheduling against the label but note that workloads cannot control the FIPS mode of their nodes by specifying kubernetes.azure.com/fips_enabled: true. The actual FIPS mode of provisioned nodes is still controlled by the field on the AKSNodeClass.
  • As before, FIPS capability only works in NAP, not OSS Karpenter.

How was this change tested?

Does this change impact docs?

  • Yes, PR includes docs updates
  • Yes, issue opened: #
  • No

Release Note

add support for scheduling against kubernetes.azure.com/fips_enabled

tallaxes
tallaxes previously approved these changes Feb 18, 2026
…abled

* This adds the ability to simulate scheduling against the label but
  note that workloads cannot control the FIPS mode of their nodes by
  specifying kubernetes.azure.com/fips_enabled: true. The actual FIPS
  mode of provisioned nodes is still controlled by the field on the
  AKSNodeClass.
* As before, FIPS capability only works in NAP, not OSS Karpenter.
@matthchr matthchr force-pushed the matthchr/fips-label branch from 1599e3d to 1bd5057 Compare February 19, 2026 17:07
@matthchr
Copy link
Member Author

E2E uncovered a (test) issue, where I had failed to add the label to the should support well-known labels for instance type selection test.

I've fixed that and requeued a fresh E2E

@matthchr matthchr force-pushed the matthchr/fips-label branch from e1718cf to 88230ac Compare February 20, 2026 21:38
Comment on lines +2347 to +2348
testOptions.UseSIG = true
ctx = options.ToContext(ctx, testOptions)
Copy link
Collaborator

@tallaxes tallaxes Feb 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't this (once executed) persist for subsequent tests here? (Even if yes, maybe it does not matter since tests pass, but feels weird ...)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ctx = options.ToContext(ctx, test.Options()) is in BeforeEach, so I think no?

Copy link
Collaborator

@tallaxes tallaxes Feb 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, yes, so ctx should be fine. But top-level BeforeEach also does test.ApplyDefaultStatus(nodeClass, env, testOptions.UseSIG), do we care about images in status? Probably not ...

@matthchr matthchr force-pushed the matthchr/fips-label branch from 88230ac to f045386 Compare February 21, 2026 00:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants