<?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>article Error when applying the custom resource on GKE in Troubleshooting</title>
    <link>https://community.dynatrace.com/t5/Troubleshooting/Error-when-applying-the-custom-resource-on-GKE/ta-p/230207</link>
    <description>&lt;PRE&gt;&lt;CODE&gt;Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "webhook.dynatrace.com": Post "https://dynatrace-webhook.dynatrace.svc:443/validate?timeout=2s (https://dynatrace-webhook.dynatrace.svc/validate?timeout=2s)": context deadline exceeded
  &lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;If you are getting this error when trying to apply the custom resource on your GKE cluster, the firewall is blocking requests from the Kubernetes API to the Dynatrace Webhook because the required port (8443) is blocked by default.&lt;/P&gt;
&lt;P&gt;The default allowed ports (443 and 10250) on GCP refer to the ports exposed by your nodes and pods, not the ports exposed by any Kubernetes services. For example, if the cluster control plane attempts to access a service on port 443 such as the Dynatrace webhook, but the service is implemented by a pod using port 8443, this is blocked by the firewall.&lt;/P&gt;
&lt;P&gt;To fix this, &lt;A href="https://dt-url.net/5k03vyk" target="_blank"&gt;add a firewall rule&lt;/A&gt; to explicitly allow ingress to port 8443.&lt;/P&gt;
&lt;P&gt;For more information about this issue, see &lt;A href="https://dt-url.net/f323v04" target="_blank"&gt;API request that triggers admission webhook timing out&lt;/A&gt;.&lt;/P&gt;</description>
    <pubDate>Wed, 06 Dec 2023 08:59:58 GMT</pubDate>
    <dc:creator>darynakovyrina</dc:creator>
    <dc:date>2023-12-06T08:59:58Z</dc:date>
    <item>
      <title>Error when applying the custom resource on GKE</title>
      <link>https://community.dynatrace.com/t5/Troubleshooting/Error-when-applying-the-custom-resource-on-GKE/ta-p/230207</link>
      <description>&lt;PRE&gt;&lt;CODE&gt;Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "webhook.dynatrace.com": Post "https://dynatrace-webhook.dynatrace.svc:443/validate?timeout=2s (https://dynatrace-webhook.dynatrace.svc/validate?timeout=2s)": context deadline exceeded
  &lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;If you are getting this error when trying to apply the custom resource on your GKE cluster, the firewall is blocking requests from the Kubernetes API to the Dynatrace Webhook because the required port (8443) is blocked by default.&lt;/P&gt;
&lt;P&gt;The default allowed ports (443 and 10250) on GCP refer to the ports exposed by your nodes and pods, not the ports exposed by any Kubernetes services. For example, if the cluster control plane attempts to access a service on port 443 such as the Dynatrace webhook, but the service is implemented by a pod using port 8443, this is blocked by the firewall.&lt;/P&gt;
&lt;P&gt;To fix this, &lt;A href="https://dt-url.net/5k03vyk" target="_blank"&gt;add a firewall rule&lt;/A&gt; to explicitly allow ingress to port 8443.&lt;/P&gt;
&lt;P&gt;For more information about this issue, see &lt;A href="https://dt-url.net/f323v04" target="_blank"&gt;API request that triggers admission webhook timing out&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Dec 2023 08:59:58 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Troubleshooting/Error-when-applying-the-custom-resource-on-GKE/ta-p/230207</guid>
      <dc:creator>darynakovyrina</dc:creator>
      <dc:date>2023-12-06T08:59:58Z</dc:date>
    </item>
  </channel>
</rss>

