Cerise Norling
Cerise Norling
> Same as above, xADGroup can do this Sorry, I glazed over that functionality and ended up missing it. > xADWaitForServiceAccount, combine both sMSA and gMSA tests in there. Most...
On `xADInstallSingleManagedServiceAccount` I would worry about the MSA being installed on two different nodes. There should probably be some kind of check to make sure there's not already a valid...
In my workplace, we clear the kerberos tickets with `klist purge –li 0x3e7` and the GMSA works without a reboot. @kungfu71186 to chime off of your process, we usually work...
One concern I have with `xADWaitForServiceAccount` being a separate DSC resource is if `xADManagedServiceAccounts` passes its tests and `xADWaitForServiceAccount` does not, you are limited with what `xADWaitForServiceAccount` can do to...
I'm sorry, I should have opened a pull request years ago for this content to be added in. I built it as I thought it should be and didn't think...
There might be some way to use the `podMonitoring` resource to listen on a service that I'm just not aware of. Here's an example yaml based on the `prom-example` example...
That's pretty much what we're doing right now, it just translates into more work for services like argocd that have multiple published metrics locations.
I'm the owner of this now deleted account FYI
I'm doing some parallel work around this area (hosting a minecraft server in GKE) and would love to work together with you on this!
I don't see `volume.path` from the values yaml digested anywhere, is it used?