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

feat(shield): add support for windows host-shield #2184

Draft
wants to merge 16 commits into
base: main
Choose a base branch
from

Conversation

francesco-furlan
Copy link
Contributor

What this PR does / why we need it:

Checklist

  • Title of the PR starts with type and scope, (e.g. feat(agent,node-analyzer,sysdig-deploy):)
  • Chart Version bumped for the respective charts
  • Variables are documented in the README.md (or README.tpl in some charts)
  • Check GithubAction checks (like lint) to avoid merge-check stoppers
  • All test files are added in the tests folder of their respective chart and have a "_test" suffix

@francesco-furlan francesco-furlan force-pushed the feat/shield-support-for-windows branch 2 times, most recently from 251959f to 031a16a Compare March 26, 2025 16:44
@francesco-furlan francesco-furlan force-pushed the feat/shield-support-for-windows branch from 031a16a to ce0db6c Compare March 27, 2025 09:43
Comment on lines +26 to +41
{{/*
Same as "shield.fullname" but for Windows
*/}}
{{- define "shield.windows.fullname" -}}
{{- if .Values.fullname_override }}
{{- printf "%s-%s" "windows" .Values.fullname_override | trunc 63 | trimSuffix "-" }}
{{- else }}
{{- $name := (include "shield.name" .) }}
{{- if contains $name .Release.Name }}
{{- printf "%s-%s" "windows" .Release.Name | trunc 63 | trimSuffix "-" }}
{{- else }}
{{- printf "%s-%s-%s" "windows" .Release.Name $name | trunc 63 | trimSuffix "-" }}
{{- end }}
{{- end }}
{{- end }}

Copy link
Contributor

Choose a reason for hiding this comment

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

Not needed...u can simply use the shield.fullname passing host-windows.
It will also help to keep consistency between object naming<RELEASE-NAME>-<COMPONENT>

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I did it on purpose to have windows as a prefix, otherwise we could end up with the same name when release name + component is too long

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mavimo @aroberts87 we were discussing that to keep a sort of naming standard it could make sense to have somthing like <RELEASE-NAME>-windows-<COMPONENT>. Do you agree?

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