search

openshift / oc

The OpenShift Command Line, part of OKD
https://www.openshift.org
Apache License 2.0
196 stars 380 forks source link

`oc apply -k <folder-name>` fails and `kubectl -k <folder-name>` succeeds #950

Closed dalelotts closed 1 year ago

dalelotts commented 3 years ago

Reported to me by @remiserra

oc appy -k <folder-name> fails if there is a url in the kustomization file.

oc apply -k base 
error: rawResources failed to read Resources: Load from path https://raw.githubusercontent.com/tektoncd/catalog/main/task/npm/0.1/npm.yaml failed: evalsymlink failure on '.../base/https:/raw.githubusercontent.com/tektoncd/catalog/main/task/npm/0.1/npm.yaml' : lstat .../base/https:: no such file or directory

compared to kubectl which works fine.

kubectl apply -k base
task.tekton.dev/npm configured
pipeline.tekton.dev/nodejs configured

Kustimization.yaml

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- https://raw.githubusercontent.com/tektoncd/catalog/main/task/npm/0.1/npm.yaml
- nodejs.pipeline.yaml

nodejs.pipeline.yaml defines a tekton Pipeline that uses the npm task - this file does not impact the outcome, it can be anything.

Folder structure

base
├── kustomization.yaml
└── nodejs.Pipeline.yaml

macos 11.6 oc and kubectl installed with brew - ran brew update && brew upgrade and verified bug before creating this issue.

➜  oc version
Client Version: v4.2.0-alpha.0-657-g51011e4
Server Version: 4.6.44
Kubernetes Version: v1.19.0+4c3480d
➜  kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.2", GitCommit:"8b5a19147530eaac9476b0ab82980b4088bbc1b2", GitTreeState:"clean", BuildDate:"2021-09-15T21:31:32Z", GoVersion:"go1.16.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.0+4c3480d", GitCommit:"4c3480dcd4299c3b3e9a75e28d643177600e7d72", GitTreeState:"clean", BuildDate:"2021-07-09T00:02:08Z", GoVersion:"go1.15.14", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.22) and server (1.19) exceeds the supported minor version skew of +/-1
openshift-bot commented 2 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

dalelotts commented 2 years ago

/remove-lifecycle stale

After months, this has never been reviewed?

openshift-bot commented 2 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

dalelotts commented 2 years ago

/remove-lifecycle stale

After months, this has never been reviewed?

openshift-bot commented 2 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

dalelotts commented 2 years ago

/remove-lifecycle stale

Seems like no one will ever review this issue.

openshift-bot commented 2 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 2 years ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 1 year ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci[bot] commented 1 year ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/oc/issues/950#issuecomment-1334878526): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.