allow specifying wl profiles in labels #612
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces support for user-defined application profiles in the container profiling and caching logic. The main changes focus on detecting when a container is associated with a user-defined profile, retrieving and caching these profiles, and ensuring such containers are handled appropriately throughout the lifecycle management process.
User-defined profile support:
UserDefinedProfile
field to bothWatchedContainerData
andContainerInfo
structs to track if a container uses a user-defined profile. [1] [2]SetContainerInfo
method to extract the user-defined profile name from pod labels and set it inWatchedContainerData
.addContainer
method inApplicationProfileCacheImpl
to:UserDefinedProfile
field inContainerInfo
.Profile cache and state management:
Dependency update:
github.com/kubescape/k8s-interface
dependency to versionv0.0.200
ingo.mod
.How to use:
nginx-user-defined