Ansible-man

Results 23 comments of Ansible-man

ClamAV is unusable on FIPS-enabled Linux systems due to MD5 use

I second this. It needs to be addressed ASAP

Bug in mattermost-team-edition readiness probe

It looks like there is already a PR in for this. What will it take to get this merged? https://github.com/mattermost/mattermost-helm/pull/448

Zarf overwrites namespace labels required when deploying to env with restricted pod security standard

Yes @AustinAbro321 . Please see https://kubernetes.io/docs/concepts/security/pod-security-standards/ https://kubernetes.io/docs/concepts/security/pod-security-admission/ https://kubernetes.io/docs/concepts/security/pod-security-admission/#exemptions Because PSA is enforcing the restricted Pod Security Level and Zarf does not apply security context to its deployment like spec: securityContext:...

Zarf overwrites namespace labels required when deploying to env with restricted pod security standard

I would be more than happy to do testing and put in a PR to apply the proper security context on the zarf-agent if its something you guys want. The...

Zarf overwrites namespace labels required when deploying to env with restricted pod security standard

@AustinAbro321 Sounds good, I will look into doing this in the next few days. Thanks

Zarf overwrites namespace labels required when deploying to env with restricted pod security standard

I have it on my calendar to do this next week.

Zarf overwrites namespace labels required when deploying to env with restricted pod security standard

@AustinAbro321 I have the code ready to commit, I can't seem to make a branch or access the slack channel. I read the contributing docs and I see where it...

Zarf overwrites namespace labels required when deploying to env with restricted pod security standard

Tested the above in my rke2 cluster at home with the restricted PSS and all seemed to go well. We only deploy the zarf agent without any other components so...

Zarf adds package to package list even if deployment fails

Maybe the feature could add another collum to the output of zarf package list that shows the deployment status? We also have a use case to track the last patch...

Zarf publishes empty packages to private repo when package name is not specified

Would it a good idea to add a flag to allow zarf publish to publish a zarf packages found in a directory when a directory is passed as the argument?...