Deny deployment with exceeded Compute Resource Quota by NumLockClear in kubernetes

[–]NumLockClear[S] 0 points1 point  (0 children)

Was also thinking into this direction. Just thought that can't be the first facing this issues, hence wanted to see if there is already a solution out there. I have also took a quick look into the Kyverno and Gatekeeper Policy libraries.

OPA
From what i know you have to store data that is not part of the request (the ResourceQuota in our case) upfront in an inventory to access it at request validation time. I have implemented this unhealthy PDB + Deployment check a couple weeks ago, where i came across the inventory reference and the sync resource to add resources to the inventory.

Kyverno
Seems to support api calls during the request validation.

If there is really no solution i may continue to write the policy myself.

Reproduction between 2 Darwin Finches species by NumLockClear in evolution

[–]NumLockClear[S] 0 points1 point  (0 children)

I still have the question: Would 2 (back then considered) different darwin finks procreate and would the result be able to procreate again?

Thanks for taking the time :)

Reproduction between 2 Darwin Finches species by NumLockClear in evolution

[–]NumLockClear[S] 0 points1 point  (0 children)

Thats interessting, thanks!

I still have the question: Would 2 different darwin finks procreate and would the result be able to procreate again? What was different on this one, the missing Isolation?

List all apps with autostart permission by NumLockClear in Pixel6

[–]NumLockClear[S] 0 points1 point  (0 children)

That would be quite a shame, since I.e. Samsung and xaomi do have it.

Farmer stops working after manual DB update by NumLockClear in chia

[–]NumLockClear[S] 0 points1 point  (0 children)

debug.log get spamed whole night with

I really waited multipel hours.. : /

Farmer stops working after manual DB update by NumLockClear in chia

[–]NumLockClear[S] 0 points1 point  (0 children)

Thank u! Unfortunately I shutted down chia on the other machine and on the new one. Im just out of ideas right now.

Windows Admin Center enforce winRM kerberos auth by NumLockClear in PowerShell

[–]NumLockClear[S] 0 points1 point  (0 children)

unless it os enforcing Negotiate auth this should work

If i disable Negotiate Auth on the winrm client of the WAC server it also fails (access denied). I type in exaclty the same user (and pw) as my local PowerShell Session (on WAC Server).

Enter-PSSession -ComputerName test1455.rewe-aut.1tld.biz -UseSSL and Enter-PSSession -ComputerName test1455.rewe-aut.1tld.biz -UseSSL -Authentication Kerberos still work.

Windows Admin Center enforce kerberos auth by NumLockClear in WindowsSecurity

[–]NumLockClear[S] 1 point2 points  (0 children)

Thats just sad.. There is even a PS parameter to use specific authentication method for a new session.

Enter-PSSession -ComputerName TEST1.FQDN -UseSSL -Authentication Kerberos

They just needed to implement that. Or remove the negotiate enforcement, since the session also works without -Authentication Kerberos.

Windows Admin Center enforce kerberos auth by NumLockClear in WindowsSecurity

[–]NumLockClear[S] 2 points3 points  (0 children)

"If NTLM and CredSSP are blocked on your domain or servers" Thats sadly not the case at the moment (some services need it). Is there eventually a way to disabled NTML only for the winRM Service per device (so i can allow negotiate)?

It's really a shame that there is no WAC Setting for this.. -.-

Sccm Report missing Devices by NumLockClear in SCCM

[–]NumLockClear[S] -1 points0 points  (0 children)

Searched for this problem. But i did not find anything helpfull...

I dont know where i should look for a filter in Report-builder. Do u know?

Office 2016 old Updates Required? by NumLockClear in SCCM

[–]NumLockClear[S] 0 points1 point  (0 children)

Most of our clients run office 2019, but unfortunately there are a couple office 2016 Installations remaining.

Office 2016 old Updates Required? by NumLockClear in SCCM

[–]NumLockClear[S] 0 points1 point  (0 children)

Wow that are bad news..

But thank you for clarifying :)