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

Resurrect extensions/v1beta1.HPA #14037

Closed
wants to merge 6 commits into from
Closed

Conversation

ncdc
Copy link
Contributor

@ncdc ncdc commented May 3, 2017

Based on #14021 but with rewritten history to include updated protobuf etc from kube. I'm not sure why the autoscaling/v2alpha1 proto is importing extensions/v1beta1, but I assume genprotobuf knows what it's doing...

@ncdc
Copy link
Contributor Author

ncdc commented May 3, 2017

[test]

@ncdc
Copy link
Contributor Author

ncdc commented May 3, 2017

cc @smarterclayton re proto import question

@ncdc
Copy link
Contributor Author

ncdc commented May 3, 2017

@sttts note, in order to regen the swagger spec in kube, I had to do this in our kube fork:

diff --git a/hack/update-swagger-spec.sh b/hack/update-swagger-spec.sh
index bce02a7..b8b9172 100755
--- a/hack/update-swagger-spec.sh
+++ b/hack/update-swagger-spec.sh
@@ -67,6 +67,8 @@ kube::log::status "Starting kube-apiserver"
   --etcd-servers="http://${ETCD_HOST}:${ETCD_PORT}" \
   --advertise-address="10.10.10.10" \
   --cert-dir="${TMP_DIR}/certs" \
+  --runtime-config="batch/v2alpha1" \
+  --runtime-config="autoscaling/v2alpha1" \
   --service-cluster-ip-range="10.0.0.0/24" >/tmp/swagger-api-server.log 2>&1 &
 APISERVER_PID=$!

@openshift-bot
Copy link
Contributor

Evaluated for origin test up to 045cafa

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/1134/) (Base Commit: 4a5ee06)

@ncdc
Copy link
Contributor Author

ncdc commented May 4, 2017

Stefan is going to finish this in his copy, closing mine

@ncdc ncdc closed this May 4, 2017
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

Successfully merging this pull request may close these issues.

3 participants