Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can we take over? #13

Open
unn opened this issue Aug 20, 2024 · 3 comments
Open

Can we take over? #13

unn opened this issue Aug 20, 2024 · 3 comments

Comments

@unn
Copy link

unn commented Aug 20, 2024

Hi @slicen,

I work at Linode/Akamai. My team recently forked your repo but we were wondering if you would be willing to transfer ownership of it over to us? We appreciate the work you have done over the past several years and were hoping to continue the effort.

Thanks!

@diegodambra
Copy link

Thank you! Please let us know when we have a working docker image (we should trust).

@unn
Copy link
Author

unn commented Sep 6, 2024

We rolled a 0.3.0 which should get you past the incompatibility issues with the recent Kube versions.

@diegodambra
Copy link

Leaving comment for other getting warnings about deprecated API calls. The forked repo by Linode fixed the issue in our GCP K8s environment. Fix was to update image in deployment.yaml with the docker image mentioned above.

Deprecated API calls:

/apis/flowcontrol.apiserver.k8s.io/v1beta2/prioritylevelconfigurations
/apis/flowcontrol.apiserver.k8s.io/v1beta2/flowschemas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants