Ross Williams

I ran into this issue as well. Seems the author may be inactive. https://github.com/jawshooah/homebrew-pyenv/issues/1

> For anyone having problems they think are related to the TLS/EOF messages, make sure you take note of what @irbekrm says above. Correct, the certificates seem to be provisioned...

Going to drop my $0.02 here and share the use case. We are rebuilding our IAM across all of our accounts with AWS SSO as the entry point to our...

We have just hit this issue as well with a new SSO implementation. This will be fine with the CLI as I have a separate role we will assume there...

> One option - not simply - is to watch for changes to IAM roles (AWS Config, or EventBridge) and then use that update feed to drive updates to controller-managed...

Why is this labeled `more info needed`? I think this is an obvious use case particularly if you want your users to use assumed roles with least privilege. In our...

I ran into this running the QEMU image on Proxmox. I did think it was a bit weird that the core user was automatically logged in, and I could interact...

> > I addressed this by creating a second user in my ignition config and removing passwordless sudo and docker access from the core user. > > Or you can...

> The new Alpha has Ignition v3 which includes the "kargs" directive to set kernel parameters and reboot from the initramfs to make them match the expected values > >...

This is how I did it: ``` --- apiVersion: v1 kind: PersistentVolume metadata: annotations: pv.kubernetes.io/provisioned-by: rancher.io/local-path name: pv-retain-vault spec: accessModes: - ReadWriteOnce capacity: storage: 10Gi claimRef: apiVersion: v1 kind: PersistentVolumeClaim...