Hi Team,

The current state of the README.md is:

TODO: ADD README.md here

It's been like this since 01c7eec

Is there any chance we can get a TLDR written into this; Hopefully one that describes a short list of services that are expected to be handed off to the openshift-apiserver and why it exists?

This will make it a lot easier for the support-staff when troubleshooting API-related issues.

Cheers,
Michael

OpenShift currently has support for BitBucket, GitHub, and GitLab. However, it'd be great if Pagure was also natively supported in OpenShift, especially as Fedora increasingly uses OpenShift for running services (either through their main OpenShift instance or the Communishift instance).

Pagure's webhook system is similar to GitLab's and GitHub's and should be relatively easy to integrate with. Sample payloads are documented with fedmsg. If there is any data/fields missing, please let @pypingou or myself know so we can look to add it to Pagure.

#23 has added private copies of:

• pkg/image/apiserver/registries (at the time from openshift/machine-config-operator) now available in openshift-runtime-utils/pkg/registries)
• pkg/image/apiserver/sysregistriesv2 (from containers/image/pkg/sysregistriesv2)

It would be nice to instead vendor the upstream code, so that we can use all the existing vendoring tools to recognize/manage outdated dependencies and their updates.

(OTOH, it would drag in a few more not really used dependencies: #23 (comment) #23 (comment) .)

E0211 12:59:19.703718 19 wrap.go:54] timeout or abort while handling: method=GET URI="/apis/template.openshift.io/v1/templateinstances?allowWatchBookmarks=true&resourceVersion=52489&timeout=6m49s&timeoutSeconds=409&watch=true" audit-ID="b0a35b5f-17f7-44b4-bfa2-ff17525f9872"
E0211 12:59:19.722265 19 wrap.go:54] timeout or abort while handling: method=GET URI="/apis/route.openshift.io/v1/routes?allowWatchBookmarks=true&resourceVersion=52489&timeout=8m28s&timeoutSeconds=508&watch=true" audit-ID="ba21701a-5c36-4929-bd96-bdbadd309a87"
E0211 12:59:20.556152 19 wrap.go:54] timeout or abort while handling: method=GET URI="/apis/build.openshift.io/v1/builds?allowWatchBookmarks=true&resourceVersion=58046&timeout=6m5s&timeoutSeconds=365&watch=true" audit-ID="19b6c3f9-38f3-4f9c-acd8-bf9413479ad3"
E0211 12:59:24.437018 19 wrap.go:54] timeout or abort while handling: method=GET URI="/apis/image.openshift.io/v1/imagestreams?allowWatchBookmarks=true&resourceVersion=665503&timeout=6m2s&timeoutSeconds=362&watch=true" audit-ID="ab5cafa4-8934-4750-a166-67d88f7be662"
E0211 12:59:26.915270 19 wrap.go:54] timeout or abort while handling: method=GET URI="/apis/apps.openshift.io/v1/deploymentconfigs?allowWatchBookmarks=true&resourceVersion=52506&timeout=8m24s&timeoutSeconds=504&watch=true" audit-ID="5d7fe004-24e4-4533-aec4-7f6ecbd0bbc4"
E0211 12:59:27.747743 19 wrap.go:54] timeout or abort while handling: method=GET URI="/apis/template.openshift.io/v1/brokertemplateinstances?allowWatchBookmarks=true&resourceVersion=52503&timeout=5m40s&timeoutSeconds=340&watch=true" audit-ID="bcea3626-0fc4-476b-a5a9-afbda0d4a546"
E0211 12:59:28.810936 19 wrap.go:54] timeout or abort while handling: method=GET URI="/apis/build.openshift.io/v1/buildconfigs?allowWatchBookmarks=true&resourceVersion=52369&timeout=7m55s&timeoutSeconds=475&watch=true" audit-ID="fb96a4cb-9716-489e-9847-f2fa8121b081"
E0211 12:59:28.896780 19 wrap.go:54] timeout or abort while handling: method=GET URI="/apis/oauth.openshift.io/v1/useroauthaccesstokens?allowWatchBookmarks=true&resourceVersion=52502&timeout=9m26s&timeoutSeconds=566&watch=true" audit-ID="bfb999c8-8bd8-4fca-a87a-c66a8fcbce1d"
E0211 12:59:28.991341 19 wrap.go:54] timeout or abort while handling: method=GET URI="/apis/template.openshift.io/v1/templates?allowWatchBookmarks=true&resourceVersion=52496&timeout=7m17s&timeoutSeconds=437&watch=true" audit-ID="906617cd-05be-4625-99f7-0825ae1cc4ea"
E0211 12:59:29.265106 19 wrap.go:54] timeout or abort while handling: method=GET URI="/apis/security.openshift.io/v1/rangeallocations?allowWatchBookmarks=true&resourceVersion=52489&timeout=7m17s&timeoutSeconds=437&watch=true" audit-ID="3f058e9f-1a61-4aa7-9ee5-5ecd1eb6f1ac"
E0211 12:59:29.704176 19 wrap.go:54] timeout or abort while handling: method=GET URI="/apis/template.openshift.io/v1/templateinstances?allowWatchBookmarks=true&resourceVersion=52489&timeout=9m0s&timeoutSeconds=540&watch=true" audit-ID="87173d21-a8b4-4408-bf46-5c4edf95509e"
E0211 12:59:29.722730 19 wrap.go:54] timeout or abort while handling: method=GET URI="/apis/route.openshift.io/v1/routes?allowWatchBookmarks=true&resourceVersion=52489&timeout=5m45s&timeoutSeconds=345&watch=true" audit-ID="3b692bb1-13b4-48dc-9f8a-53280f66e371"
E0211 12:59:30.556852 19 wrap.go:54] timeout or abort while handling: method=GET URI="/apis/build.openshift.io/v1/builds?allowWatchBookmarks=true&resourceVersion=58046&timeout=9m45s&timeoutSeconds=585&watch=true" audit-ID="3435b7d5-9249-48d3-8d64-d11976531462"

this is familiar with this https://bugzilla.redhat.com/show_bug.cgi?id=1922949

Hello!

Can you please advice about the license of this repo? Is it Apache 2.0 or you don't allow reuse this repo?

Thanks in advance!

I want export openshift resource defination like CRD YAML file, which import to k8s api server.

from openshift:
oc get crd project.openshift.io > project_crd.yaml

to k8s
kubectl apply -f project_crd.yaml

why i want do this?
Because I use karmada component for mulit cluster management, my member clusters is openshift. karmada control panel only support kube-apiserver, which not have Project resource.

@dmage @benluddy @bparees I hope I am at the correct place here, found this online for context:

Image streams are part of the OpenShift extension APIs. Other OpenShift extension resources, such as build configurations and deployment configurations, provide native support for image streams. OpenShift tooling, such as the oc command, offers easy-to-use commands to manage image stream resources, as well as other extension API resources.
OpenShift adds its extension APIs using standard Kubernetes extension mechanisms, such as custom resource definitions (CRDs) and admission plugins. This feature allows OpenShift to support using image streams together with standard Kubernetes workload API resources, such as Deployments, StatefulSets, and Jobs.

When I have an imagestream in the same namespace as a StatefulSet, I cannot use the image field and reference imagestream name and tag there. It does not get resolved.

In contrast, when I reference the imagestream from a DeploymentConfig, or from a Pod, or from a Deployment, the image name and digest get resolved correctly, as it should be.

Should this not have been fixed in the admission controller or something like that a long time ago, for all kinds of objects?

See https://bugzilla.redhat.com/show_bug.cgi?id=2000216 and https://access.redhat.com/solutions/6455191

In any case, the expected result would be: image stream tags get resolved in created and edited StatefulSets.

The following branches are being fast-forwarded from the current development branch (master) as placeholders for future releases. No merging is allowed into these release branches until they are unfrozen for production release.

• release-4.16
• release-4.17

For more information, see the branching documentation.