Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: soltysh Assign the PR to them by writing The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these OWNERS Files:You can indicate your approval by writing |
| api/types/registry \ | ||
| api/types/strslice \ | ||
| api/types/swarm \ | ||
| api/types/versions |
There was a problem hiding this comment.
wow, if this goes away finally
|
|
||
| // TODO: Remove jsoniter for now as it is buggy and fails the serialization | ||
| // test for DockerImage objects. | ||
| /* |
There was a problem hiding this comment.
Can you add more info to the commit message? What fails? Do we have a test-case? Can we open an issue in the upstream project?
| writer = cmdutil.NewGLogWriterV(0) | ||
| } | ||
| backend = auditlog.NewBackend(writer, auditlog.FormatLegacy) | ||
| backend = auditlog.NewBackend(writer, auditlog.FormatLegacy, auditv1alpha1.SchemeGroupVersion) |
There was a problem hiding this comment.
I don't want to do it in the rebase, I'll do it post, I have a trello card for it.
| return nil, errors.NewInternalError(fmt.Errorf("unable to connect to server: %v", err)) | ||
| } | ||
| streamOptions := remotecommand.StreamOptions{ | ||
| SupportedProtocols: kubeletremotecommand.SupportedStreamingProtocols, |
There was a problem hiding this comment.
That's still broken, that's one of the pieces I need to revisit.
There was a problem hiding this comment.
@soltysh is there a follow up issue or note somewhere so we don't forget?
|
Re-synced k8s bump commit and rebased against this morning master, but it appears there are some problems in the k8s pr. I'll sync with @mfojtik tomorrow and figure this out. |
533ef94 to
419f26d
Compare
pkg/cmd/server/origin/master.go
Outdated
|
|
||
| func (c *MasterConfig) withAggregator(delegateAPIServer apiserver.DelegationTarget, kubeAPIServerConfig apiserver.RecommendedConfig, apiExtensionsInformers apiextensionsinformers.SharedInformerFactory) (*aggregatorapiserver.APIAggregator, error) { | ||
| aggregatorConfig, err := c.createAggregatorConfig(kubeAPIServerConfig) | ||
| aggregatorConfig, err := c.createAggregatorConfig(kubeAPIServerConfig.Config, c.ClientGoKubeInformers) |
There was a problem hiding this comment.
Why isn't kubeAPIServerConfig.SharedInformerFactory set with a non-nil value?
This change looks suspicious, probably now hiding another error.
d141711 to
036aca0
Compare
…ump cronjob storage
8e9bea0 to
614724c
Compare
|
CI is green on 8e9bea0 modulo existing issues against master Squashed commits to 614724c (zero diff with 8e9bea0) no conflicts in the two commits between 79097d0...3841e1d |
|
@soltysh: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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. I understand the commands that are listed here. |
@mfojtik @sttts @liggitt @deads2k @ironcladlou you can slowly start looking into it.
Rebase status:
make buildmake build-testfollow ups:
images/dockerregistry, resolve pulling docker-registry for e2e? - Remove dockerregistry Dockerfile and build #17388source-to-imageto stop using engine-api - Drop engine api source-to-image#834oc clusterto stop using engine-apidocker.io/...- opened bzrelease notes - added to openshift/openshift-docs#6458
{}->[] breaks)