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.

Sign up for GitHub

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

Jump to bottom

Use Ingress for CI on GKE. #534

Closed
spxtr opened this issue Sep 8, 2016 · 1 comment
Closed

Use Ingress for CI on GKE. #534

spxtr opened this issue Sep 8, 2016 · 1 comment
Assignees
@spxtr
Labels
area/prow Issues or PRs related to prow

Comments

@spxtr
Copy link
Contributor

spxtr commented Sep 8, 2016 •
edited
Loading

Currently I'm getting strange flakes when I try to use any LB. Once those are resolved, switch back. The workaround is to expose a NodePort, which isn't ideal.
@spxtr spxtr added the area/prow Issues or PRs related to prow label Sep 8, 2016
@spxtr spxtr self-assigned this Sep 8, 2016
@spxtr
Copy link
Contributor Author

spxtr commented Sep 12, 2016

kubernetes/kubernetes#32415

@spxtr spxtr closed this as completed Sep 12, 2016
ostromart pushed a commit to ostromart/test-infra that referenced this issue Jul 26, 2019
@yutongz @istio-merge-robot
Make sure release-note is none (kubernetes#534)
0bf4587 
Automatic merge from submit-queue.

Make sure release-note is none

**Release note**:

```release-note
none
```

istio/old_pilot_repo#1402
grantr pushed a commit to grantr/test-infra that referenced this issue Feb 21, 2020
@srinivashegde86 @knative-prow-robot
Use FormatLogger instead of BaseLogger in prometheus wrapper (kuberne…
b74ea40 
…tes#534)

* Use FormatLogger instead of BaseLogger in prometheus wrapper

* Add missing errors pkg in vendor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@spxtr spxtr

Labels
area/prow Issues or PRs related to prow
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@spxtr