Ishwar Kanse
Ishwar Kanse
+1 for LXD support. We are using LXD in production at University of Mumbai and it would be really great if ansible-container could support LXD. We are currently building our...
It would be helpful if users have queries on the article or a tutorial is not working for them.
@iblancasa I'll check and update the issue.
@iblancasa There are no PodSecurity warnings anymore, I checked in OpenShift 4.15. However the instrumentation tests needs to be updated as the asserts are wrong. I was manually running the...
@iblancasa @jaronoff97 We can close this issue as we are not running into the PodSecurity warnings anymore. Also I have resolved issues with asserts, security contexts in this PR, pending...
@rubenvp8510 Fixed the upgrade test. Direct resource support was removed from Chainsaw 0.2.4 version. https://github.com/kyverno/chainsaw/releases/tag/v0.2.4 We now have to specify the apiVersion and kind for the resource. https://kyverno.github.io/chainsaw/latest/operations/helpers/get/
We would like to see this feature too. Some of our tests depend on the cluster env, cloud provider and auth types. For example, we are currently running these tests...
@max-cx In the step 3 in https://docs.openshift.com/container-platform/4.12/otel/otel-sending-traces-and-metrics-to-otel-collector.html#sending-traces-and-metrics-to-otel-collector-without-sidecar_otel-sending-traces-and-metrics-to-otel-collector The serviceaccount name in the subjects must be otel-collector-deployment like below. ``` apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: name: otel-collector subjects: - kind: ServiceAccount...
These RBAC are not documented for the processor. https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/k8sattributesprocessor