Thomas Mueller

@mookie- for me ``` puppet apply --strict_variables -e 'notify { "bla $doesnotexist": }' puppet apply -e 'notify { "bla $doesnotexist": }' ``` works as expected: ``` $ puppet apply --strict_variables...

@walkleyn can you paste the complete commandline you ouse and the complete output of octocatalog-diff?

@kpaulisse `$server_facts` is a IMHO compile time top-scope variable only. https://puppet.com/docs/puppet/latest/lang_facts_and_builtin_vars.html#serverfacts-variable

@kpaulisse and the setting is deprecated and always true: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/defaults.rb#L654 what puppet apply does with server_facts seems to be this: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/application/apply.rb#L238

@markdanko I don't think octocatalog-diff resolves anything other than "puppet" - as it calls puppet to compile. There were bugs in Puppet 3 which allowed to resolve variables that actually...

I can see this warning also on OpenShift 4.8 (K8s 1.21). Can't find documentation about the "hard expiry" time on OpenShift. [Feature docs]((https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/)): > BoundServiceAccountTokenVolume: Migrate ServiceAccount volumes to use...

the token is already changed by k8s periodically. Only the user of the token needs to reload it from disk. IMHO "vanilla" fluentd doesnt use the k8s api. it's the...

@harshit-splunk probably tomorrow I can test the hvaghani/fluentd-hec image. The other components we don't use.

@harshit-splunk pods with `hvaghani/fluentd-hec:1.2.13-refresh-token` are running 3 hours now. I don't see any `annotations.authentication.k8s.io/stale-token` in audit logs on OpenShift 4.8. According pod definition the token expires after 3607 seconds (`expirationSeconds:...

I can't confirm this behaviour. started 2 containers. the addnhosts file looks this: ``` $ cat /run/user/1000/rootless-cni/run/user/1000/containers/cni/dnsname/test/addnhosts 10.89.0.2 container-a 10.89.0.3 container-b ``` then ran `podman stop container-a` + `podman start...