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

Deprecated UltraDns API #2780

Closed
slimshetty opened this issue May 31, 2022 · 14 comments
Closed

Deprecated UltraDns API #2780

slimshetty opened this issue May 31, 2022 · 14 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@slimshetty
Copy link

What happened:
External Dns failing to create dns records in UltraDns. The domain name filter that is provided is tv3cloud.com , but external dns is skipping records with this domain name.

POD LOGS
time="2022-05-31T08:07:41Z" level=info msg="Skipping record txt-k8sprom-a.play.mr.tv3cloud.com. because no hosted zone matching record DNS Name was detected"

DEPLOYMENT ARGS:
args:

  • --source=service

  • --source=ingress

  • --domain-filter=tv3cloud.com

  • --provider=ultradns

  • --txt-prefix=txt-

  • --registry=txt

What you expected to happen:
The records matching the domain should be created

How to reproduce it (as minimally and precisely as possible):
Setup a zone in ultradns, create a deployment of external dns using the ultradns provider, check if dns records are created

Anything else we need to know?:
I raised a support ticket with external dns and found out that the zones api is deprecated (https://api.ultradns.com/zones/) and replaced by -> https://api.ultradns.com/v3/zones/

i have tried changing the base url in the deployment from https://api.ultradns.com/zones/ to https://api.ultradns.com/v3/zones/ but it gave me 404 not found. However when i tried the new url from postman it worked. I suppose there are some changes required from external dns to support the new api??

Environment:

  • External-DNS version (use external-dns --version): 0.10.2
  • DNS provider: UltraDns
  • Others:
@slimshetty slimshetty added the kind/bug Categorizes issue or PR as related to a bug. label May 31, 2022
@Volatus
Copy link
Contributor

Volatus commented Jul 4, 2022

@slimshetty Could you try running at a verbosity level and post the results?

@slimshetty
Copy link
Author

@Volatus I have pasted both the debug level and verbose level( --log-level=warning ) logs below. pls note i have edited the debug logs to hide the record names and ips. From the debug logs it is clear that the ultradns api (https://api.ultradns.com/zones/?&q=name:tv3cloud.com&offset=0&limit=1000) is not returning any zones and hence external dns is not matching our records. The api needs to be updated to https://api.ultradns.com/v3/zones/

DEBUG LEVEL

2022/07/05 05:11:31 [DEBUG] HTTP Request: &{Method:GET URL:https://api.ultradns.com/zones/?&q=name:tv3cloud.com&offset=0&limit=1000 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Accept:[application/json] Content-Type:[application/json] Ultraclient:[kube-client] User-Agent:[udnssdk-go/0.1]] Body:{} GetBody:0x6c0780 ContentLength:0 TransferEncoding:[] Close:false Host:api.ultradns.com Form:map[] PostForm:map[] MultipartForm: Trailer:map[] RemoteAddr: RequestURI: TLS: Cancel: Response: ctx:0xc000058018}
2022/07/05 05:11:32 [DEBUG] HTTP Response: &{Status:200 OK StatusCode:200 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Access-Control-Allow-Headers:[Origin, X-Requested-With, Content-Type, Accept, Authorization, UltraClient] Access-Control-Allow-Methods:[POST, GET, OPTIONS, DELETE, PUT, PATCH] Access-Control-Allow-Origin:[] Access-Control-Max-Age:[3600] Connection:[keep-alive] Content-Type:[application/json] Date:[Tue, 05 Jul 2022 05:11:32 GMT] Vary:[Origin Access-Control-Request-Method Access-Control-Request-Headers Accept-Encoding, User-Agent]] Body:0xc0015ac4a0 ContentLength:-1 TransferEncoding:[chunked] Close:false Uncompressed:true Trailer:map[] Request:0xc000244500 TLS:0xc0015c8000}
time="2022-07-05T05:11:32Z" level=info msg="endpoints []"
time="2022-07-05T05:11:32Z" level=info msg="value of changes [test.dns.record.tv3cloud.com 300 IN A {ipaddress} [] txt-test.dns.record.tv3cloud.com 0 IN TXT "heritage=external-dns,external-dns/owner=mr-play-A,external-dns/resource=ingress/monitoring/test" []],[],[]"
2022/07/05 05:11:32 [DEBUG] HTTP Request: &{Method:GET URL:https://api.ultradns.com/zones/?&q=name:tv3cloud.com&offset=0&limit=1000 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Accept:[application/json] Content-Type:[application/json] Ultraclient:[kube-client] User-Agent:[udnssdk-go/0.1]] Body:{} GetBody:0x6c0780 ContentLength:0 TransferEncoding:[] Close:false Host:api.ultradns.com Form:map[] PostForm:map[] MultipartForm: Trailer:map[] RemoteAddr: RequestURI: TLS: Cancel: Response: ctx:0xc000058018}
2022/07/05 05:11:32 [DEBUG] HTTP Response: &{Status:200 OK StatusCode:200 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Access-Control-Allow-Headers:[Origin, X-Requested-With, Content-Type, Accept, Authorization, UltraClient] Access-Control-Allow-Methods:[POST, GET, OPTIONS, DELETE, PUT, PATCH] Access-Control-Allow-Origin:[
] Access-Control-Max-Age:[3600] Connection:[keep-alive] Content-Type:[application/json] Date:[Tue, 05 Jul 2022 05:11:32 GMT] Vary:[Origin Access-Control-Request-Method Access-Control-Request-Headers Accept-Encoding, User-Agent]] Body:0xc0003907a0 ContentLength:-1 TransferEncoding:[chunked] Close:false Uncompressed:true Trailer:map[] Request:0xc00067cf00 TLS:0xc0015c8000}
time="2022-07-05T05:11:32Z" level=info msg="Skipping record test.dns.record.tv3cloud.com. because no hosted zone matching record DNS Name was detected"

VERBOSE LEVEL

2022/07/05 05:20:40 [DEBUG] HTTP Response: &{Status:200 OK StatusCode:200 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Access-Control-Allow-Headers:[Origin, X-Requested-With, Content-Type, Accept, Authorization, UltraClient] Access-Control-Allow-Methods:[POST, GET, OPTIONS, DELETE, PUT, PATCH] Access-Control-Allow-Origin:[] Access-Control-Max-Age:[3600] Connection:[keep-alive] Content-Type:[application/json] Date:[Tue, 05 Jul 2022 05:20:39 GMT] Vary:[Origin Access-Control-Request-Method Access-Control-Request-Headers Accept-Encoding, User-Agent]] Body:0xc000af3780 ContentLength:-1 TransferEncoding:[] Close:false Uncompressed:true Trailer:map[] Request:0xc00046eb00 TLS:0xc0001aa0b0}
2022/07/05 05:21:40 [DEBUG] HTTP Request: &{Method:GET URL:https://api.ultradns.com/zones/?&q=name:tv3cloud.com&offset=0&limit=1000 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Accept:[application/json] Content-Type:[application/json] Ultraclient:[kube-client] User-Agent:[udnssdk-go/0.1]] Body:{} GetBody:0x6c0780 ContentLength:0 TransferEncoding:[] Close:false Host:api.ultradns.com Form:map[] PostForm:map[] MultipartForm: Trailer:map[] RemoteAddr: RequestURI: TLS: Cancel: Response: ctx:0xc000114000}
2022/07/05 05:21:40 [DEBUG] HTTP Response: &{Status:200 OK StatusCode:200 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Access-Control-Allow-Headers:[Origin, X-Requested-With, Content-Type, Accept, Authorization, UltraClient] Access-Control-Allow-Methods:[POST, GET, OPTIONS, DELETE, PUT, PATCH] Access-Control-Allow-Origin:[
] Access-Control-Max-Age:[3600] Connection:[keep-alive] Content-Type:[application/json] Date:[Tue, 05 Jul 2022 05:21:40 GMT] Vary:[Origin Access-Control-Request-Method Access-Control-Request-Headers Accept-Encoding, User-Agent]] Body:0xc0011120c0 ContentLength:-1 TransferEncoding:[chunked] Close:false Uncompressed:true Trailer:map[] Request:0xc00046e200 TLS:0xc0001aa0b0}
2022/07/05 05:21:40 [DEBUG] HTTP Request: &{Method:GET URL:https://api.ultradns.com/zones/?&q=name:tv3cloud.com&offset=0&limit=1000 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Accept:[application/json] Content-Type:[application/json] Ultraclient:[kube-client] User-Agent:[udnssdk-go/0.1]] Body:{} GetBody:0x6c0780 ContentLength:0 TransferEncoding:[] Close:false Host:api.ultradns.com Form:map[] PostForm:map[] MultipartForm: Trailer:map[] RemoteAddr: RequestURI: TLS: Cancel: Response: ctx:0xc000114000}
2022/07/05 05:21:41 [DEBUG] HTTP Response: &{Status:200 OK StatusCode:200 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Access-Control-Allow-Headers:[Origin, X-Requested-With, Content-Type, Accept, Authorization, UltraClient] Access-Control-Allow-Methods:[POST, GET, OPTIONS, DELETE, PUT, PATCH] Access-Control-Allow-Origin:[] Access-Control-Max-Age:[3600] Connection:[keep-alive] Content-Type:[application/json] Date:[Tue, 05 Jul 2022 05:21:40 GMT] Vary:[Origin Access-Control-Request-Method Access-Control-Request-Headers Accept-Encoding, User-Agent]] Body:0xc00013a880 ContentLength:-1 TransferEncoding:[] Close:false Uncompressed:true Trailer:map[] Request:0xc00136ae00 TLS:0xc0001aa0b0}
2022/07/05 05:22:41 [DEBUG] HTTP Request: &{Method:GET URL:https://api.ultradns.com/zones/?&q=name:tv3cloud.com&offset=0&limit=1000 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Accept:[application/json] Content-Type:[application/json] Ultraclient:[kube-client] User-Agent:[udnssdk-go/0.1]] Body:{} GetBody:0x6c0780 ContentLength:0 TransferEncoding:[] Close:false Host:api.ultradns.com Form:map[] PostForm:map[] MultipartForm: Trailer:map[] RemoteAddr: RequestURI: TLS: Cancel: Response: ctx:0xc000114000}
2022/07/05 05:22:41 [DEBUG] HTTP Response: &{Status:200 OK StatusCode:200 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Access-Control-Allow-Headers:[Origin, X-Requested-With, Content-Type, Accept, Authorization, UltraClient] Access-Control-Allow-Methods:[POST, GET, OPTIONS, DELETE, PUT, PATCH] Access-Control-Allow-Origin:[
] Access-Control-Max-Age:[3600] Connection:[keep-alive] Content-Type:[application/json] Date:[Tue, 05 Jul 2022 05:22:41 GMT] Vary:[Origin Access-Control-Request-Method Access-Control-Request-Headers Accept-Encoding, User-Agent]] Body:0xc00013b280 ContentLength:-1 TransferEncoding:[chunked] Close:false Uncompressed:true Trailer:map[] Request:0xc000c12e00 TLS:0xc0001aa0b0}
2022/07/05 05:22:41 [DEBUG] HTTP Request: &{Method:GET URL:https://api.ultradns.com/zones/?&q=name:tv3cloud.com&offset=0&limit=1000 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Accept:[application/json] Content-Type:[application/json] Ultraclient:[kube-client] User-Agent:[udnssdk-go/0.1]] Body:{} GetBody:0x6c0780 ContentLength:0 TransferEncoding:[] Close:false Host:api.ultradns.com Form:map[] PostForm:map[] MultipartForm: Trailer:map[] RemoteAddr: RequestURI: TLS: Cancel: Response: ctx:0xc000114000}
2022/07/05 05:22:42 [DEBUG] HTTP Response: &{Status:200 OK StatusCode:200 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Access-Control-Allow-Headers:[Origin, X-Requested-With, Content-Type, Accept, Authorization, UltraClient] Access-Control-Allow-Methods:[POST, GET, OPTIONS, DELETE, PUT, PATCH] Access-Control-Allow-Origin:[*] Access-Control-Max-Age:[3600] Connection:[keep-alive] Content-Type:[application/json] Date:[Tue, 05 Jul 2022 05:22:41 GMT] Vary:[Origin Access-Control-Request-Method Access-Control-Request-Headers Accept-Encoding, User-Agent]] Body:0xc001113b00 ContentLength:-1 TransferEncoding:[] Close:false Uncompressed:true Trailer:map[] Request:0xc00046f900 TLS:0xc0001aa0b0}

Volatus added a commit to Volatus/external-dns that referenced this issue Jul 5, 2022
The UltraDNS SDK was outdated by about 2 years or more.
There has been many new releases of the SDK that's more stable so we
should update.

Might also help with kubernetes-sigs#2780

Signed-off-by: Ismayil Mirzali <[email protected]>
@Volatus
Copy link
Contributor

Volatus commented Jul 5, 2022

@slimshetty I've gone through the code and made a PR to update the Go SDK for UltraDNS to be a much newer version, hoping that fixes the problem. If the PR gets merged, this thread will close but feel free to reopen the issue and @ me and I'll take what we can do to fix it.

@slimshetty
Copy link
Author

@Volatus i made these changes locally and built a new image. Tested the new image it did not fix the issue. I also tried changing the ultradns base url to https://api.ultradns.com/v3/ after that i see these 404 logs

time="2022-07-06T10:04:27Z" level=error msg="Get "https://api.ultradns.com/v3/zones/?&q=name:tv3cloud.com&offset=0&limit=1000\": oauth2: cannot fetch token: 404 Not Found\nResponse: [{"errorCode":404,"errorMessage":"Not Found"}]"
2022/07/06 10:05:28 [DEBUG] HTTP Request: &{Method:GET URL:https://api.ultradns.com/v3/zones/?&q=name:tv3cloud.com&offset=0&limit=1000 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Accept:[application/json] Content-Type:[application/json] Ultraclient:[kube-client] User-Agent:[udnssdk-go/0.1]] Body:{} GetBody:0x6c5300 ContentLength:0 TransferEncoding:[] Close:false Host:api.ultradns.com Form:map[] PostForm:map[] MultipartForm: Trailer:map[] RemoteAddr: RequestURI: TLS: Cancel: Response: ctx:0xc000196000}
2022/07/06 10:05:28 [DEBUG] HTTP Response:
time="2022-07-06T10:05:28Z" level=error msg="Get "https://api.ultradns.com/v3/zones/?&q=name:tv3cloud.com&offset=0&limit=1000\": oauth2: cannot fetch token: 404 Not Found\nResponse: [{"errorCode":404,"errorMessage":"Not Found"}]"
2022/07/06 10:06:28 [DEBUG] HTTP Request: &{Method:GET URL:https://api.ultradns.com/v3/zones/?&q=name:tv3cloud.com&offset=0&limit=1000 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Accept:[application/json] Content-Type:[application/json] Ultraclient:[kube-client] User-Agent:[udnssdk-go/0.1]] Body:{} GetBody:0x6c5300 ContentLength:0 TransferEncoding:[] Close:false Host:api.ultradns.com Form:map[] PostForm:map[] MultipartForm: Trailer:map[] RemoteAddr: RequestURI: TLS: Cancel: Response: ctx:0xc000196000}
2022/07/06 10:06:28 [DEBUG] HTTP Response:
time="2022-07-06T10:06:28Z" level=error msg="Get "https://api.ultradns.com/v3/zones/?&q=name:tv3cloud.com&offset=0&limit=1000\": oauth2: cannot fetch token: 404 Not Found\nResponse: [{"errorCode":404,"errorMessage":"Not Found"}]

@Volatus
Copy link
Contributor

Volatus commented Jul 6, 2022

@slimshetty
image

@slimshetty
Copy link
Author

slimshetty commented Jul 6, 2022

@Volatus Updating the ultradns sdk and calling the ultradns api using the base url https://api.ultradns.com/zones did not work, still not returning any zones.
I had sent support request to ultradns on these apis and this is what i got from them

Thank you for contacting Neustar UltraDNS.
The URL provided in your API call has been deprecated. Please follow the steps below to migrate to our new API for the following calls.
Change 1: Steps for migrating to List Metadata for Zones – v3
Add the /v3 version in your URL as shown below:
Your existing URL -
https://api.ultradns.com/zones
https://api.ultradns.com/v1/zones
https://api.ultradns.com/v2/zones
Your new URL
https://api.ultradns.com/v3/zones

I dont think they have updated the docs , also the golang ultradns sdk has not been updated since 2020
https://github.com/ultradns/ultradns-sdk-go

I think we should use this sdk instead which is more up to date and uses /v3 to get zones info
https://github.com/ultradns/ultradns-go-sdk
.
I manually tested the apis with /v3 and without any versioning through postman and only the /v3 api is working .

@Volatus
Copy link
Contributor

Volatus commented Jul 6, 2022

@Volatus Updating the ultradns sdk and calling the ultradns api using the base url https://api.ultradns.com/zones did not work, still not returning any zones. I had sent support request to ultradns on these apis and this is what i got from them

Thank you for contacting Neustar UltraDNS.
The URL provided in your API call has been deprecated. Please follow the steps below to migrate to our new API for the following calls.
Change 1: Steps for migrating to List Metadata for Zones – v3
Add the /v3 version in your URL as shown below:
Your existing URL -
https://api.ultradns.com/zones
https://api.ultradns.com/v1/zones
https://api.ultradns.com/v2/zones
Your new URL
https://api.ultradns.com/v3/zones

I dont think they have updated the docs , also the golang ultradns sdk has not been updated since 2020 https://github.com/ultradns/ultradns-sdk-go

I think we should use this sdk instead which is more up to date and uses /v3 to get zones info https://github.com/ultradns/ultradns-go-sdk . I manually tested the apis with /v3 and without any versioning through postman and only the /v3 api is working .

@slimshetty If the 2nd SDK you mentioned worked with your testing, then I can look into migrating the provider to the other one. Can you confirm it worked with the v3 API on the new SDK?

@slimshetty
Copy link
Author

@Volatus instead of using the new sdk which would require to rewrite the entire ultradns.go I updated the zones uri in the existing sdk. Along with the uri there are some changes to the pagination info the api returns. It does not return ResultInfo anymore and instead returns CursorInfo with page id of first, next , previous and last pages. More details on the change can be found here : https://docs.ultradns.neustar/Content/REST%20API/Content/REST%20API/Zone%20API/Zone%20API.htm

Tested these changes locally and built an image and all functionality seems to be working fine now, will soon raise a PR here

@shettyvaishak
Copy link

@Volatus can you help with raising a pr here i am not able to, i have updated the sdk and tested it out locally there seems to be no issues. I was not able to update the existing repo so i forked it and made the changes
https://github.com/shettyvaishak/ultradns-sdk-go

Along with updating the imports also need to update the pagination logic currently the logic is to get the resultInfo and use offset to query the api but this has been changed to cursorinfo and page id, so it will require few changes in ultradns.go and ultradns_test.go. I have copied the changes i did locally to make this work into a file , can you review and raise a pr with these changes
externaldns_diff.txt

This link has more info on the updated api
https://docs.ultradns.neustar/Content/REST%20API/Content/REST%20API/Zone%20API/Zone%20API.htm

@Volatus
Copy link
Contributor

Volatus commented Jul 16, 2022

@Volatus can you help with raising a pr here i am not able to, i have updated the sdk and tested it out locally there seems to be no issues. I was not able to update the existing repo so i forked it and made the changes https://github.com/shettyvaishak/ultradns-sdk-go

Along with updating the imports also need to update the pagination logic currently the logic is to get the resultInfo and use offset to query the api but this has been changed to cursorinfo and page id, so it will require few changes in ultradns.go and ultradns_test.go. I have copied the changes i did locally to make this work into a file , can you review and raise a pr with these changes externaldns_diff.txt

This link has more info on the updated api https://docs.ultradns.neustar/Content/REST%20API/Content/REST%20API/Zone%20API/Zone%20API.htm

@shettyvaishak Sure I can try and help out. The diff you provided does not apply though, can you make sure your fork is up-to-date with the upstream and recreate the patch? You can email it to me. (email should be available on github profile) You can create the patch using git format-patch -1 HEAD. This will create a patch from the latest commit. (make sure it's your commit) Or you can do git format-patch -1 <sha> with the specific commit sha to make the patch.

@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 14, 2022
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 13, 2022
@k8s-triage-robot
Copy link

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

This bot triages 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:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

/close not-planned

@k8s-ci-robot k8s-ci-robot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 13, 2022
@k8s-ci-robot
Copy link
Contributor

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
5 participants