Feature request: yandex cloud provider support

[ArtemTrofimushkin]

What would you like to be added:

Support for Yandex cloud dns zone management

Why is this needed:

Convenient dns records management for clusters, that running on Yandex Cloud managed service for Kubernetes platform

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[artem-zinnatullin]

As long as Yandex operates in Russia ruled by authoritarian government, Yandex.News shows only government-affiliated propaganda (in general and with regards to Russian war with Ukraine),

Yandex.Taxi will be sharing private data with FSB and I'm sure government will keep creating more laws that'll effectively be turning dozens of Yandex services and their tremendous datasets of user data into a digital gulag for anyone not agreeing with the Russian government, I don't think k8s projects should cooperate with Yandex related feature requests and support tickets.

Open source is open source, sure, Yandex can use k8s and other OSS projects as long as it doesn't violate their license, but cooperation is not necessary.

[ytsarev]

@artem-zinnatullin I personally don't care about yandex but imho open source as a scientific work should be above any political agenda. Please, don't bring this stuff to our wonderful world of intellectual collaboration.

[artem-zinnatullin]

@ytsarev comparing support of a commercial API to scientific work is a far stretch.

One could say that Yandex.Cloud actually allows people to run their websites in which they can voice their opinions, which is true. But make no mistake, Yandex will gladly comply with Russian censorship and will deny you service as they did with all non-government media in Yandex.News, Yandex.Music, Yandex.Dzen.

Btw, I'm a Yandex shareholder and and ex-employee, if anyone thinks it's another anon hater — sad to disappoint you.

[ytsarev]

@artem-zinnatullin I understand your point but would be super concerned to create a case when we are not accepting contribution ( or just an idea of contribution ) based on the political narrative. It can be just dangerous and harmful to the community in the long run.

[artem-zinnatullin]

@ytsarev

super concerned to create a case when we are not accepting contribution ( or just an idea of contribution ) based on the political narrative

Concern you have is valid and I respect it quite a lot, it's always politics and there is very little truth in it. Maintaining an OSS project that is available for everyone is great.

By no means I'm arguing in favor of calling in for a government-like monopoly on power to regulate this or similar cases, whether it's political sanctions of other regimes or say GitHub Support. What I do want however is to remind project maintainers that they have all the rights to refuse any type of support to any type of individual or legal entity according to the project's LICENSE section №7:

7. Disclaimer of Warranty. Unless required by applicable law or
   agreed to in writing, Licensor provides the Work (and each
   Contributor provides its Contributions) on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND

Project maintainers can consider any detail of a given interaction to make their decision on accepting a PR or providing other forms of support (including this particular interaction with me). Community on the other hand has all the rights to judge maintainers' actions.

If you think that adding support for a commercial API of a company operating in a state which is considered authoritarian by many outsiders and insiders and is currently at full-scale invasion war with its neighbor is in spirit of open source mindset because it should not discriminate anyone — that's your opinion and I will stand beside you to protect your right to voice it.

My job here as someone who is likely to face criminal charges for violating government censorship by exercising my constitutional right to freedom of speech (article 29 of Russian Constitution) for my anti-war and anti-regime position if I get back to my homeland — Russia, is to remind that the world is how it is because of our individual actions. Personally, I would not cooperate with entities acting in support of authoritarian regimes when I can — but that's my opinion and I'm sure there are cases when it's wrong on a history scale.

Thanks for having this conversation, apologies for bringing politics into OSS world.

[Raffo]

As maintainer of this project, I can only say that I will ask for guidance to the Kubernetes community as this situation won't be a first. We actually already had a pretty bad case related to the situation in Ukraine, with a dependency creating a DoS to this project by making a dependency unavailable from outside or Russia.

I will not share here my personal opinion on the topic because it doesn't matter: I try to play by the rules that we agree on, trying to make this place as inclusive as possible. Politics is unfortunately part of real life and as such inevitably gets into this project.

I also want to thank you both for having a quite good discussion on such a hot topic.

[ArtemTrofimushkin]

Hi, @Raffo!
Do you have any updates/news about ability to accept related PR?

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[ArtemTrofimushkin]

/remove-lifecycle rotten

[kvendingoldo]

Any updates here?

[martysai]

Still relevant. Any updates?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[kvendingoldo]

/remove-lifecycle stale

[pauljamm]

We added external DNS with Yandex Cloud support to our marketplace.
You can install it from there
https://cloud.yandex.com/en-ru/marketplace/products/yc/externaldns

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[patsevanton]

Any updates here?

[vaibhav2107]

/remove-lifecycle stale

[kvendingoldo]

it's not stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[patsevanton]

it's not stale

[ytsarev]

/remove-lifecycle stale

[Uburro]

judging by the documentation, new providers need to be done via a webhook https://github.com/kubernetes-sigs/external-dns?tab=readme-ov-file#new-providers
#3063 - more detailed

[Raffo]

I confirm this, we are not accepting new providers. Providers can be implemented with a webhhok. Closing this issue.