-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
post-rebase TODOs #14647
Comments
|
bump coreos/etcd upstream to v3.2.1 - #15322 |
Seeing this in the logs on a real data set:
```
E0718 22:37:20.981215 74010 cacher.go:274] unexpected ListAndWatch error:
github.com/openshift/origin/vendor/k8s.io/apiserver/pkg/storage/cacher.go:215:
Failed to list *autoscaling.HorizontalPodAutoscaler: no kind
"HorizontalPodAutoscaler" is registered for version "extensions/v1beta1"
I0718 22:37:21.982476 74010 reflector.go:236] Listing and watching
*autoscaling.HorizontalPodAutoscaler from
github.com/openshift/origin/vendor/k8s.io/apiserver/pkg/storage/cacher.go:215
```
…On Tue, Jul 18, 2017 at 10:07 PM, Jordan Liggitt ***@***.***> wrote:
bump coreos/etcd upstream to v3.2.1 - #15322
<#15322>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#14647 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABG_p-ae_dc5Ns4Pmav3ATBZ4PLpR9N0ks5sPWTugaJpZM4N6Ndo>
.
|
did you run |
Did we drop support for that in 1.6? Because this is restore from a backup
onto 1.7
…On Tue, Jul 18, 2017 at 10:41 PM, Jordan Liggitt ***@***.***> wrote:
did you run oadm migrate? should be written to autoscaling v1.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#14647 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABG_py-QSi6_IBlu-0Hy8aG1l3RICkiSks5sPWzRgaJpZM4N6Ndo>
.
|
dropped support in 1.7. upstream dropped it in 1.5, we carried it in 1.6 to allow the migrate |
Ok, something I can test then
…On Tue, Jul 18, 2017 at 10:48 PM, Jordan Liggitt ***@***.***> wrote:
dropped support in 1.7
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#14647 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABG_p5biSJnjTsVGtrbjGW3GdIzgYTK3ks5sPW6NgaJpZM4N6Ndo>
.
|
Attach looks broken on Mac @fabianofranz
I hit enter and nothing ever happens. Did we fix something like this in upstream? If I hit CTRL+C I get:
|
Which is novel. |
@deads2k all TODOs seem ticked |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
UPSTREAM: <carry>: make namespace lifecycle access review aware
should be fixed by discovery. If you can't get it, then it's not really stored. - Remove ns lifecycle carry #15255UPSTREAM: <carry>: Disable file locking in clientcmd
why would we do this. Seems like it gets removed upstream or we deal with it. - RemoveUPSTREAM: <carry>: Disable file locking in clientcmd
#15257UPSTREAM: <carry>: match kube rbac setup in e2es with openshift kinds
drop when we move to RBAC authorizer - removeUPSTREAM: <carry>: match kube rbac setup in e2es with openshift kinds
#15258UPSTREAM: 00000: disambiguate operation names for legacy discovery
move upstream - Move upstreamUPSTREAM: 00000: disambiguate operation names for legacy discovery
#15259UPSTREAM: <drop>: drop post 3.7 rebase. allows disabled aggregator
force aggregator always on and remove this - Remove UPSTREAM: <drop>: drop post 3.7 rebase. allows disabled aggregator #15260UPSTREAM: <carry>: Add our types to kubectl get error
should be handled generically. upstream needs to discover too - remove UPSTREAM: <carry>: Add our types to kubectl get error #15261UPSTREAM: <carry>: add kubelet timeouts
move upstream - move timeout increases upstream #15256UPSTREAM: <carry>: Allow overriding default generators for run
- just fix the upstream already - move UPSTREAM: <carry>: Allow overriding default generators for run #15262UPSTREAM: <carry>: fix fifo resync, remove after FIFO is dead
fix this whereever it needs fixing - remove UPSTREAM: <carry>: fix fifo resync, remove after FIFO is dead #15263UPSTREAM: <carry>: Fix to avoid REST API calls at log level 2.
- move upstream or drop it @aveshagarwal - remove UPSTREAM: <carry>: Fix to avoid REST API calls at log level 2. #15264UPSTREAM: <drop>: Set the log level for iptables rule dump to 5
- move upstream or drop it (ben bennet) - remove UPSTREAM: <drop>: Set the log level for iptables rule dump to 5 #15265UPSTREAM: <drop>: keep old pod available
#15274NewBuilder
function in the factory from upstream #15278GetNodeCondition
#15283disable go version checking
#15270WithAudit
filter. Now we do onlyWithLegacyAudit
. - Wire up the newWithAudit
filter #15271if _, err := url.Parse(o.RegistryUrlOverride); err != nil {
inpkg/cmd/admin/prune/images.go
- add back validation (maybe?) fordisable registry url validation in prune
#15291InfraPersistentVolumeRecyclerControllerServiceAccountName
creation inpkg/cmd/server/start/start_master.go
- cleanup creation of InfraPersistentVolumeRecyclerControllerServiceAccountName #15292The text was updated successfully, but these errors were encountered: