Skip to content

Fix accessing a GKE cluster through the private endpoint in GKEStartPodOperator - #31391

Merged
potiuk merged 2 commits into
apache:mainfrom
hussein-awala:gcp/fix_gke_opp
May 23, 2023
Merged

Fix accessing a GKE cluster through the private endpoint in GKEStartPodOperator#31391
potiuk merged 2 commits into
apache:mainfrom
hussein-awala:gcp/fix_gke_opp

Conversation

@hussein-awala

Copy link
Copy Markdown
Member

closes: #31387

In this PR, I reuse the parameter use_internal_ip which was removed in #29266 to allow the users to use the private endpoint to access the GKE cluster in the operator GKEStartPodOperator.


^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

@boring-cyborg boring-cyborg Bot added provider:cncf-kubernetes Kubernetes (k8s) provider related issues area:providers provider:google Google (including GCP) related issues labels May 18, 2023
Comment on lines -436 to -443
if use_internal_ip is not None:
warnings.warn(
f"You have set parameter use_internal_ip in class {self.__class__.__name__}. "
"In current implementation of the operator the parameter is not used and will "
"be deleted in future.",
AirflowProviderDeprecationWarning,
stacklevel=2,
)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why was it deprecated to begin with?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was deprecated (technically removed with deprecation warning) in #29266.

It seems like they assumed that the new connection method can connect to any cluster through the public IP, without considering that some users disable access to their cluster from the public network, and that the current method always returns the public IP, even when public access is disabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:providers provider:cncf-kubernetes Kubernetes (k8s) provider related issues provider:google Google (including GCP) related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GKEStartPodOperator cannot connect to Private IP after upgrade to 2.6.x

3 participants