Provide mechanism for opting cloud proxy out of listening on an ipv6 address #2013
Labels
Comments
This was referenced Sep 9, 2024
ddelnano
added a commit
that referenced
this issue
Sep 18, 2024
…igmap mount directory) (#2027) Summary: Fix cloud proxy entrypoint by avoiding modifying a RO directory (Configmap mount directory) This bug was introduced between 0a44b36 and c3e0fba on #2018 when the individual file mounts were changed to a directory mount. Deploying the cloud proxy from main results in the following error: ``` $ kubectl -n plc logs cloud-proxy-5df85487bf-hrglr Defaulted container "cloud-proxy-server" out of: cloud-proxy-server, envoy /scripts/entrypoint.sh: line 20: can't create /usr/local/openresty/nginx/conf/nginx.conf: Read-only file system ``` When I originally tested the final change, I must have only looked at the resulting directory and missed that the pod was crashing. This issue was detected during the 0.1.8 cloud prerelease testing. Relevant Issues: #2017 #2013 Type of change: /kind bugfix Test Plan: Verified that the cloud proxy image starts up successfully Signed-off-by: Dom Del Nano <[email protected]>
ddelnano
added a commit
to ddelnano/pixie
that referenced
this issue
Sep 23, 2024
…igmap mount directory) (pixie-io#2027) Summary: Fix cloud proxy entrypoint by avoiding modifying a RO directory (Configmap mount directory) This bug was introduced between 0a44b36 and c3e0fba on pixie-io#2018 when the individual file mounts were changed to a directory mount. Deploying the cloud proxy from main results in the following error: ``` $ kubectl -n plc logs cloud-proxy-5df85487bf-hrglr Defaulted container "cloud-proxy-server" out of: cloud-proxy-server, envoy /scripts/entrypoint.sh: line 20: can't create /usr/local/openresty/nginx/conf/nginx.conf: Read-only file system ``` When I originally tested the final change, I must have only looked at the resulting directory and missed that the pod was crashing. This issue was detected during the 0.1.8 cloud prerelease testing. Relevant Issues: pixie-io#2017 pixie-io#2013 Type of change: /kind bugfix Test Plan: Verified that the cloud proxy image starts up successfully Signed-off-by: Dom Del Nano <[email protected]> GitOrigin-RevId: 1f96cff
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A slack community member reported that the cloud proxy service will fail to start if it's deployed to an instance that has ipv6 disabled. This manifests through the following error and happens because of this line.
Ideally the cloud proxy service could be configured to avoid trying to listen on this address. This could be driven via an environment variable, so that end users that need this behavior can opt into it.
The text was updated successfully, but these errors were encountered: