<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Cloud-Native setup in non-privileged Kubernetes cluster in Container platforms</title>
    <link>https://community.dynatrace.com/t5/Container-platforms/Cloud-Native-setup-in-non-privileged-Kubernetes-cluster/m-p/259420#M2712</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/43077"&gt;@Lukas_Lorinc&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;One of my clients follow these steps, they also used helm on OKD. Have you done the #2?&lt;/P&gt;&lt;P&gt;# Dynatrace cloudnativefullstack install on OKD 4.16&lt;/P&gt;&lt;P&gt;# 1. install CSI driver (&lt;A href="https://github.com/Dynatrace/dynatrace-operator" target="_blank"&gt;https://github.com/Dynatrace/dynatrace-operator&lt;/A&gt;)&lt;BR /&gt;oc create namespace dynatrace&lt;BR /&gt;oc apply -f &lt;A href="https://github.com/Dynatrace/dynatrace-operator/releases/latest/download/kubernetes.yaml" target="_blank"&gt;https://github.com/Dynatrace/dynatrace-operator/releases/latest/download/kubernetes.yaml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;# 2. add label to csidriver&lt;BR /&gt;oc label csidriver csi.oneagent.dynatrace.com security.openshift.io/csi-ephemeral-volume-profile=restricted&lt;/P&gt;&lt;P&gt;# 3. install the Dynakube instance with CloudnativeFullstack mode:&lt;BR /&gt;oc apply -f dynakube-cloudnativefullstack.yaml&lt;/P&gt;&lt;P&gt;I hope it helps.&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Mizső&lt;/P&gt;</description>
    <pubDate>Wed, 16 Oct 2024 08:02:27 GMT</pubDate>
    <dc:creator>Mizső</dc:creator>
    <dc:date>2024-10-16T08:02:27Z</dc:date>
    <item>
      <title>Cloud-Native setup in non-privileged Kubernetes cluster</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Cloud-Native-setup-in-non-privileged-Kubernetes-cluster/m-p/259398#M2708</link>
      <description>&lt;P class=""&gt;&lt;SPAN&gt;Hi everybody,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;On last Friday (11th), we were attempting to deploy Dynatrace-operator 1.3.0 cloud-native via helm deployment.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;The deployment was “stalled” by a requirement for privileged mode in the cluster:&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;Error: UPGRADE FAILED: release dynatrace-operator failed, and has been rolled back due to atomic being set: failed to create resource: DaemonSet.apps "dynatrace-oneagent-csi-driver" is invalid: [spec.template.spec.containers[0].volumeMounts.mountPropagation: Forbidden: Bidirectional mount propagation is available only to privileged containers, spec.template.spec.containers[1].volumeMounts.mountPropagation: Forbidden: Bidirectional mount propagation is available only to privileged containers]&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;We tried to bypass this with some labeling on the Dynatrace namespace (Dynatrace documentation):&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;Name:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; dynatrace&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;Labels:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; kubernetes.io/metadata.name=dynatrace&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;pod-security.kubernetes.io/audit=privileged&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;pod-security.kubernetes.io/enforce=privileged&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;pod-security.kubernetes.io/warn=privileged&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;Annotations:&amp;nbsp; &amp;lt;none&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;Status:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Active&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;This did not have the desired effect. Does anybody have similiar issue in the past?&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;Best regards,&lt;/P&gt;&lt;P class=""&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Wed, 16 Oct 2024 06:40:06 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Cloud-Native-setup-in-non-privileged-Kubernetes-cluster/m-p/259398#M2708</guid>
      <dc:creator>Lukas_Lorinc</dc:creator>
      <dc:date>2024-10-16T06:40:06Z</dc:date>
    </item>
    <item>
      <title>Re: Cloud-Native setup in non-privileged Kubernetes cluster</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Cloud-Native-setup-in-non-privileged-Kubernetes-cluster/m-p/259420#M2712</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/43077"&gt;@Lukas_Lorinc&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;One of my clients follow these steps, they also used helm on OKD. Have you done the #2?&lt;/P&gt;&lt;P&gt;# Dynatrace cloudnativefullstack install on OKD 4.16&lt;/P&gt;&lt;P&gt;# 1. install CSI driver (&lt;A href="https://github.com/Dynatrace/dynatrace-operator" target="_blank"&gt;https://github.com/Dynatrace/dynatrace-operator&lt;/A&gt;)&lt;BR /&gt;oc create namespace dynatrace&lt;BR /&gt;oc apply -f &lt;A href="https://github.com/Dynatrace/dynatrace-operator/releases/latest/download/kubernetes.yaml" target="_blank"&gt;https://github.com/Dynatrace/dynatrace-operator/releases/latest/download/kubernetes.yaml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;# 2. add label to csidriver&lt;BR /&gt;oc label csidriver csi.oneagent.dynatrace.com security.openshift.io/csi-ephemeral-volume-profile=restricted&lt;/P&gt;&lt;P&gt;# 3. install the Dynakube instance with CloudnativeFullstack mode:&lt;BR /&gt;oc apply -f dynakube-cloudnativefullstack.yaml&lt;/P&gt;&lt;P&gt;I hope it helps.&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Mizső&lt;/P&gt;</description>
      <pubDate>Wed, 16 Oct 2024 08:02:27 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Cloud-Native-setup-in-non-privileged-Kubernetes-cluster/m-p/259420#M2712</guid>
      <dc:creator>Mizső</dc:creator>
      <dc:date>2024-10-16T08:02:27Z</dc:date>
    </item>
  </channel>
</rss>

