[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-5141":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":23,"hasPages":23,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":37,"readmeContent":38,"aiSummary":39,"trendingCount":16,"starSnapshotCount":16,"syncStatus":40,"lastSyncTime":41,"discoverSource":42},5141,"origin","openshift\u002Forigin","openshift","Conformance test suite for OpenShift","http:\u002F\u002Fwww.openshift.org",null,"Go",8658,4776,447,120,0,1,6,15,5,72.5,"Apache License 2.0",false,"main",[26,27,28,29,30,31,32,33,34,7,35,36],"caas","ci-cd","containers","continuous-delivery","continuous-deployment","continuous-integration","devops","go","kubernetes","openshift-origin","paas","2026-06-12 04:00:24","Origin Kubernetes\n=================\n\n[![Go Report Card](https:\u002F\u002Fgoreportcard.com\u002Fbadge\u002Fgithub.com\u002Fopenshift\u002Forigin)](https:\u002F\u002Fgoreportcard.com\u002Freport\u002Fgithub.com\u002Fopenshift\u002Forigin)\n[![GoDoc](https:\u002F\u002Fgodoc.org\u002Fgithub.com\u002Fopenshift\u002Forigin?status.png)](https:\u002F\u002Fgodoc.org\u002Fgithub.com\u002Fopenshift\u002Forigin)\n[![Licensed under Apache License version 2.0](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Flicense\u002Fopenshift\u002Forigin.svg?maxAge=2592000)](https:\u002F\u002Fwww.apache.org\u002Flicenses\u002FLICENSE-2.0)\n\nThis repo was previously the core Kubernetes tracking repo for\n[OKD](https:\u002F\u002Fgithub.com\u002Fopenshift\u002Fokd), and where OpenShift's\n`hyperkube` and `openshift-test` binaries were maintained. As of July\n2020, the purpose and maintenance strategy of the repo varies by\nbranch.\n\n## Maintenance of `main` and `release-x.x` branches for 4.6 and above\n\nThese branches no longer include the code required to produce\n`hyperkube` binaries, and are limited to maintaining the `openshift-tests`\nbinary.  Responsibility for maintaining hyperkube has transitioned to\nthe [openshift\u002Fkubernetes](https:\u002F\u002Fgithub.com\u002Fopenshift\u002Fkubernetes)\nrepo.\n\nBackports and carries against upstream should be proposed to\n`openshift\u002Fkubernetes`. If changes merged to `openshift\u002Fkubernetes`\nneed to land in `origin`, it will be necessary to follow up with a PR\nto `origin` that bumps the vendoring.\n\nBranch names are correlated across the 2 repositories such that\nchanges merged to a given branch in `openshift\u002Fkubernetes` should be\nvendored into the same branch in `origin` (e.g. `master` in\n`openshift\u002Fkubernetes` is vendored into `main` in `origin`).\n\n**NOTE:** Vendoring of the `main` and `release-x.x` branches of\n`openshift\u002Fkubernetes` into the equivalent branches in `origin` is\nintended to be temporary. At some point in the near future, `origin`\nwill switch to vendoring origin-specific branches (e.g\n`origin-4.6-kubernetes-1.19.2`) to minimize the scope of backports and\ncarries that need to be considered in the context of\n`openshift\u002Fkubernetes` rebases.\n\n### Test exclusion rules\n\nTest exclusion is now handled through environmental selector based filtering\nrather than test annotations. Environmental selectors allow tests to be\nfiltered or skipped based on the cluster environment and configuration.\nFor example, selectors can be defined that match kube e2e tests that are\nknown to be incompatible with specific OpenShift configurations and exclude\nthose tests from running.\n\nMaintenance of test exclusion rules is split between the\n`openshift\u002Fkubernetes` and `origin` repos to ensure that PRs proposed\nto `openshift\u002Fkubernetes` can be validated against the set of kube e2e\ntests known to be compatible with OpenShift.\n\nTest exclusion rules for kubernetes e2e tests are maintained in: https:\u002F\u002Fgithub.com\u002Fopenshift\u002Fkubernetes\u002Fblob\u002Fmaster\u002Fopenshift-hack\u002Fcmd\u002Fk8s-tests-ext:\n* [environment_selectors.go](https:\u002F\u002Fgithub.com\u002Fopenshift\u002Fkubernetes\u002Fblob\u002Fmaster\u002Fopenshift-hack\u002Fcmd\u002Fk8s-tests-ext\u002Fenvironment_selectors.go)\n* [disabled_tests.go](https:\u002F\u002Fgithub.com\u002Fopenshift\u002Fkubernetes\u002Fblob\u002Fmaster\u002Fopenshift-hack\u002Fcmd\u002Fk8s-tests-ext\u002Fdisabled_tests.go)\n\nTest exclusion rules for openshift e2e tests are maintained in: https:\u002F\u002Fgithub.com\u002Fopenshift\u002Forigin\u002Fblob\u002Fmain\u002Fpkg\u002Ftest\u002Fextensions:\n* [environment_selectors.go](https:\u002F\u002Fgithub.com\u002Fopenshift\u002Forigin\u002Fblob\u002Fmain\u002Fpkg\u002Ftest\u002Fextensions\u002Fenvironment_selectors.go)\n* [disabled_tests.go](https:\u002F\u002Fgithub.com\u002Fopenshift\u002Forigin\u002Fblob\u002Fmain\u002Fpkg\u002Ftest\u002Fextensions\u002Fdisabled_tests.go)\n\nTo update test exclusion rules for kube e2e tests, update the environmental selectors in `openshift\u002Fkubernetes`. For OpenShift e2e tests, update the selectors in `origin`.\n\n### Vendoring from `openshift\u002Fkubernetes`\n\nThese origin branches vendor `k8s.io\u002Fkubernetes` and some of its\nstaging repos (e.g. `k8s.io\u002Fapi`) from our\n[openshift\u002Fkubernetes](https:\u002F\u002Fgithub.com\u002Fopenshift\u002Fkubernetes) fork.\nUpstream staging repos are used where possible, but some tests depends\non functionality that is only present in the fork.\n\nWhen a change has merged to an `openshift\u002Fkubernetes` branch that\nneeds to be vendored into the same branch in `origin`, the\n`hack\u002Fupdate-kube-vendor.sh` helper script simplifies updating the go\nmodule configuration for all dependencies sourced from\n`openshift\u002Fkubernetes` for that branch. The script requires either the\nname of a branch or a SHA from `openshift\u002Fkubernetes`:\n\n```bash\n$ hack\u002Fupdate-kube-vendor.sh \u003Copenshift\u002Fkubernetes branch name or SHA>\n```\n\nThe script also supports performing a fake bump to validate an as-yet\nunmerged change to `openshift\u002Fkubernetes`. This can be accomplished by\nsupplying the name of a fork repo as the second argument to the\nscript:\n\n```bash\n$ hack\u002Fupdate-kube-vendor.sh \u003Cbranch name or SHA> github.com\u002Fmyname\u002Fkubernetes\n```\n\nOnce the script has executed, the vendoring changes will need to be\ncommitted and proposed to the repo.\n\n#### Working around '410 Gone' error\n\nIf the script returns '410 Gone' as per the error that follows, it may\nbe that the golang checksum server does not yet know about the target\nSHA.\n\n```\ngo: k8s.io\u002Fkubernetes@v1.21.1 (replaced by github.com\u002Fopenshift\u002Fkubernetes@v1.21.2-0.20210603185452-2dfc46b23003): verifying go.mod: g\nithub.com\u002Fopenshift\u002Fkubernetes@v1.21.2-0.20210603185452-2dfc46b23003\u002Fgo.mod: reading https:\u002F\u002Fsum.golang.org\u002Flookup\u002Fgithub.com\u002Fopenshif\nt\u002Fkubernetes@v1.21.2-0.20210603185452-2dfc46b23003: 410 Gone\n        server response: not found:\n```\n\nThe workaround is to set `GOSUMDB=off` to disable the checksum\ndatabase for the vendoring update:\n\n```bash\n$ GOSUMDB=off hack\u002Fupdate-kube-vendor.sh \u003Cbranch name or SHA>\n```\n\n## Maintenance of release-4.5, release-4.4 and release-4.3\n\nReleases prior to 4.6 continue to maintain hyperkube in the `origin`\nrepo in the `release-4.x` branches. Persistent carries and backports\nfor those branches should continue to be submitted directly to\norigin. `openshift\u002Fkubernetes` is not involved except for rebases.\n\n## End-to-End (e2e) and Extended Tests\n\nEnd to end tests (e2e) should verify a long set of flows in the\nproduct as a user would see them.  Two e2e tests should not overlap\nmore than 10% of function and are not intended to test error\nconditions in detail. The project examples should be driven by e2e\ntests. e2e tests can also test external components working together.\n\nAll e2e tests are compiled into the `openshift-tests` binary.\nTo build the test binary, run `make`.\n\nTo run a specific test, or an entire suite of tests, read\n[test\u002Fextended\u002FREADME](https:\u002F\u002Fgithub.com\u002Fopenshift\u002Forigin\u002Fblob\u002Fmain\u002Ftest\u002Fextended\u002FREADME.md)\nfor more information.\n\n## Updating external examples\n\n`hack\u002Fupdate-external-example.sh` will pull down example files from external\nrepositories and deposit them under the `examples` directory.\nRun this script if you need to refresh an example file, or add a new one.  See\nthe script and `examples\u002Fquickstarts\u002FREADME.md` for more details.\n","openshift\u002Forigin 是一个为OpenShift设计的符合性测试套件。该项目使用Go语言编写，提供了`openshift-tests`二进制文件，用于确保Kubernetes及其扩展在OpenShift环境下的兼容性和稳定性。它支持通过环境选择器来过滤或跳过不适用于特定OpenShift配置的测试用例，从而提高了测试过程的灵活性和准确性。适合于需要验证Kubernetes集群在OpenShift平台上运行情况的企业级应用开发与运维场景中使用。",2,"2026-06-11 03:02:46","top_language"]