origin

package module
v1.4.0-alpha.0 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Sep 16, 2016 License: Apache-2.0 Imports: 0 Imported by: 0

README

OpenShift Application Platform

Go Report Card GoDoc Travis Jenkins Licensed under Apache License version 2.0

OpenShift Origin is a distribution of Kubernetes optimized for continuous application development and multi-tenant deployment. Origin adds developer and operations-centric tools on top of Kubernetes to enable rapid application development, easy deployment and scaling, and long-term lifecycle maintenance for small and large teams.

Watch the full asciicast

Features:

  • Easily build applications with integrated service discovery and persistent storage.
  • Quickly and easily scale applications to handle periods of increased demand.
    • Support for automatic high availability, load balancing, health checking, and failover.
  • Push source code to your Git repository and automatically deploy containerized applications.
  • Web console and command-line client for building and monitoring applications.
  • Centralized administration and management of an entire stack, team, or organization.
    • Create reusable templates for components of your system, and iteratively deploy them over time.
    • Roll out modifications to software stacks to your entire organization in a controlled fashion.
    • Integration with your existing authentication mechanisms, including LDAP, Active Directory, and public OAuth providers such as GitHub.
  • Multi-tenancy support, including team and user isolation of containers, builds, and network communication.
    • Allow developers to run containers securely with fine-grained controls in production.
    • Limit, track, and manage the developers and teams on the platform.
  • Integrated Docker registry, automatic edge load balancing, cluster logging, and integrated metrics.

Learn More:

For questions or feedback, reach us on IRC on #openshift-dev on Freenode or post to our mailing list.

Getting Started

Installation

If you have downloaded the client tools, place the included binaries in your PATH.

Concepts

We highly recommend trying out the Origin walkthrough which covers the core concepts in Origin. The walkthrough is accompanied by a blog series on blog.openshift.com that goes into more detail. It's a great place to start.

Origin API

The Origin API is located on each server at https://<host>:8443/oapi/v1. These APIs are described via Swagger v1.2 at https://<host>:8443/swaggerapi/oapi/v1. For more, see the API documentation.

Kubernetes

If you're looking for more information about using Kubernetes or the lower level concepts that Origin depends on, see the following:

Troubleshooting

If you run into difficulties running Origin, start by reading through the troubleshooting guide.

FAQ

  1. How does Origin relate to Kubernetes?

    Origin is a distribution of Kubernetes optimized for enterprise application development and deployment, used by OpenShift 3 and Atomic Enterprise. Origin embeds Kubernetes and adds additional functionality to offer a simple, powerful, and easy-to-approach developer and operator experience for building applications in containers. Our goal is to do most of that work upstream, with integration and final packaging occurring in Origin.

    You can run the core Kubernetes server components with openshift start kubernetes, use kubectl via openshift kube, and the Origin release zips include versions of kubectl, kubelet, kube-apiserver, and other core components. You can see the version of Kubernetes included with Origin via openshift version.

  2. How does Atomic Enterprise relate to Origin and OpenShift?

    Two products are built from Origin, Atomic Enterprise and OpenShift. Atomic Enterprise adds operational centric tools to enable easy deployment and scaling and long-term lifecycle maintenance for small and large teams and applications. OpenShift provides a number of developer-focused tools on top of Atomic Enterprise such as image building, management, and enhanced deployment flows.

  3. What can I run on Origin?

    Origin is designed to run any existing Docker images. Additionally, you can define builds that will produce new Docker images using a Dockerfile.

    However, the real magic of Origin is Source-to-Image (S2I) builds, which allow developers to simply provide an application source repository containing code to build and run. It works by combining an existing S2I-enabled Docker image with application source to produce a new runnable image for your application.

    We are continuing to grow the ecosystem of Source-to-Image builder images and it's straightforward to create your own. Some of our available images include:

    Your application image can be easily extended with a database service with our database images:

  4. Why doesn't my Docker image run on OpenShift?

    Security! Origin runs with the following security policy by default:

    • Containers run as a non-root unique user that is separate from other system users
      • They cannot access host resources, run privileged, or become root
      • They are given CPU and memory limits defined by the system administrator
      • Any persistent storage they access will be under a unique SELinux label, which prevents others from seeing their content
      • These settings are per project, so containers in different projects cannot see each other by default
    • Regular users can run Docker, source, and custom builds
      • By default, Docker builds can (and often do) run as root. You can control who can create Docker builds through the builds/docker and builds/custom policy resource.
    • Regular users and project admins cannot change their security quotas.

    Many Docker containers expect to run as root (and therefore edit all the contents of the filesystem). The Image Author's guide gives recommendations on making your image more secure by default:

    • Don't run as root
    • Make directories you want to write to group-writable and owned by group id 0
    • Set the net-bind capability on your executables if they need to bind to ports <1024

    Otherwise, you can see the security documentation for descriptions on how to relax these restrictions.

  5. How do I get networking working?

    The Origin and Kubernetes network model assigns each pod (group of containers) an IP that is expected to be reachable from all nodes in the cluster. The default setup is through a simple SDN plugin with OVS - this plugin expects the port 4679 to be open between nodes in the cluster. Also, the Origin master processes need to be able to reach pods via the network, so they may require the SDN plugin.

    Other networking options are available such as Calico, Flannel, Nuage, and Weave. For a non-overlay networking solution, existing networks can be used by assigning a different subnet to each host, and ensuring routing rules deliver packets bound for that subnet to the host it belongs to. This is called host subnet routing.

  6. Why can't I run Origin in a Docker image on boot2docker or Ubuntu?

    Versions of Docker distributed by the Docker team don't allow containers to mount volumes on the host and write to them (mount propagation is private). Kubernetes manages volumes and uses them to expose secrets into containers, which Origin uses to give containers the tokens they need to access the API and run deployments and builds. Until mount propagation is configurable in Docker you must use Docker on Fedora, CentOS, or RHEL (which have a patch to allow mount propagation) or run Origin outside of a container. Tracked in this issue.

Alpha and Unsupported Kubernetes Features

Some features from upstream Kubernetes are not yet enabled in Origin, for reasons including supportability, security, or limitations in the upstream feature.

Kubernetes Definitions:

  • Alpha
    • The feature is available, but no guarantees are made about backwards compatibility or whether data is preserved when feature moves to Beta.
    • The feature may have significant bugs and is suitable for testing and prototyping.
    • The feature may be replaced or significantly redesigned in the future.
    • No migration to Beta is generally provided other than documentation of the change.
  • Beta
    • The feature is available and generally agreed to solve the desired solution, but may need stabilization or additional feedback.
    • The feature is potentially suitable for limited production use under constrained circumstances.
    • The feature is unlikely to be replaced or removed, although it is still possible for feature changes that require migration.

OpenShift uses these terms in the same fashion as Kubernetes, and adds four more:

  • Not Yet Secure
    • Features which are not yet enabled because they have significant security or stability risks to the cluster
    • Generally this applies to features which may allow escalation or denial-of-service behavior on the platform
    • In some cases this is applied to new features which have not had time for full security review
  • Potentially Insecure
    • Features that require additional work to be properly secured in a multi-user environment
    • These features are only enabled for cluster admins by default and we do not recommend enabling them for untrusted users
    • We generally try to identify and fix these within 1 release of their availability
  • Tech Preview
    • Features that are considered unsupported for various reasons are known as 'tech preview' in our documentation
    • Kubernetes Alpha and Beta features are considered tech preview, although occasionally some features will be graduated early
    • Any tech preview feature is not supported in OpenShift Container Platform except through exemption
  • Disabled Pending Migration
    • These are features that are new in Kubernetes but which originated in OpenShift, and thus need migrations for existing users
    • We generally try to minimize the impact of features introduced upstream to Kubernetes on OpenShift users by providing seamless migration for existing clusters.
    • Generally these are addressed within 1 Kubernetes release

The list of features that qualify under these labels is described below, along with additional context for why.

Feature Kubernetes OpenShift Justification
Third Party Resources Alpha (1.3) Not Yet Secure (1.2, 1.3) Third party resources are still under active development upstream.
Known issues include failure to clean up resources in etcd, which may result in a denial of service attack against the cluster.
We are considering enabling them for development environments only.
Garbage Collection Alpha (1.3) Not Yet Secure (1.3) Garbage collection will automatically delete related resources on the server, and thus given the potential for data loss we are waiting for GC to graduate to beta and have a full release cycle of testing before enabling it in Origin.
At the current time, it is possible for a malicious user to trick another user into deleting a sensitive resource (like a quota or limit resource) during deletion, which must be addressed prior to enablement.
Pet Sets Alpha (1.3) Tech Preview (1.3) Pet Sets are still being actively developed and no backwards compatibility is guaranteed. Also, Pet Sets allow users to create PVCs indirectly, and more security controls are needed to limit the potential impact on the cluster.
Init Containers Alpha (1.3) Tech Preview (1.3) Init containers are properly secured, but are not officially part of the Kubernetes API and may change without notice.
Federated Clusters Beta (1.3) Tech Preview (1.3) A Kubernetes federation server may be used against Origin clusters with the appropriate credentials today.
Known issues include tenant support in federation and the ability to have consistent access control between federation and normal clusters.
No Origin specific binary is being distributed for federation at this time.
Deployment Alpha (1.2)
Beta (1.3)
Disabled Pending Migration (1.2)
Tech Preview (1.3)
OpenShift launched with DeploymentConfigs, a more fully featured Deployment object. The upstream Deployments are enabled in OpenShift as a tech preview so users can create both Deployments and DeploymentConfigs. We plan to provide migration from Deployment Config to Deployment in future when the feature parity with the upstream Deployment object is reached.
Deployment Configs are currently a superset of Deployment features.
Replica Sets Beta (1.2)
Beta (1.3)
Disabled Pending Migration (1.2)
Tech Preview (1.3)
Replica Sets perform the same function as Replication Controllers, but have a more powerful label syntax. We are working upstream to enable a migration path forward for clusters with existing Replication Controllers deployed to be automatically migratable to Replica Sets, in order to ease the transition for clients and tooling that depend on RCs.
Ingress Alpha (1.1)
Beta (1.2, 1.3)
Disabled Pending Migration (1.2)
Tech Preview (1.3)
OpenShift launched with Routes, a more full featured Ingress object. The upstream Ingress are enabled in OpenShift as a tech preview, so users can create both Ingress and Route resources. We plan to provide migration from Route to Ingress in future when the feature parity with the upstream Ingress is reached.
Routes are currently a superset of Ingress features.
PodSecurityPolicy Alpha (1.2)
Beta (1.3)
Disabled Pending Migration (1.3)
Not Yet Secure (1.3)
OpenShift launched with SecurityContextConstraints, and then upstreamed them as PodSecurityPolicy. We plan to enable upstream PodSecurityPolicy so as to automatically migrate existing SecurityContextConstraints. PodSecurityPolicy has not yet completed a full security review, which will be part of the criteria for tech preview.
SecurityContextConstraints are a superset of PodSecurityPolicy features.
PodAntiAffinitySelectors Alpha (1.3) Not Yet Secure (1.3)
Tech Preview (1.4?)
End users are not allowed to set PodAntiAffinitySelectors that are not the node name due to the possibility of attacking the scheduler via denial of service.
NetworkPolicy Beta (1.3) Tech Preview (1.3) OpenShift's default network plugins (redhat/openshift-ovs-subnet and redhat/openshift-ovs-multitenant) do not support NetworkPolicy yet, but if you use a third-party network plugin, it might.

Please contact us if this list omits a feature supported in Kubernetes which does not run in Origin.

Contributing

You can develop locally on your host or with a virtual machine, or if you want to just try out Origin download the latest Linux server, or Windows and Mac OS X client pre-built binaries.

First, get up and running with the Contributing Guide.

All contributions are welcome - Origin uses the Apache 2 license and does not require any contributor agreement to submit patches. Please open issues for any bugs or problems you encounter, ask questions on the OpenShift IRC channel (#openshift-dev on freenode), or get involved in the Kubernetes project at the container runtime layer.

See HACKING.md for more details on developing on Origin including how different tests are setup.

If you want to run the test suite, make sure you have your environment set up, and from the origin directory run:

# run the verifiers, unit tests, and command tests
$ make check

# run a command-line integration test suite
$ hack/test-cmd.sh

# run the integration server test suite
$ hack/test-integration.sh

# run the end-to-end test suite
$ hack/test-end-to-end.sh

# run all of the tests above
$ make test

You'll need etcd installed and on your path for the integration and end-to-end tests to run, and Docker must be installed to run the end-to-end tests. To install etcd you should be able to run:

$ hack/install-etcd.sh

Some of the components of Origin run as Docker images, including the builders and deployment tools in images/builder/docker/* and 'images/deploy/*`. To build them locally run

$ hack/build-images.sh

To hack on the web console, check out the assets/README.md file for instructions on testing the console and building your changes.

License

Origin is licensed under the Apache License, Version 2.0.

Documentation

Overview

This is the source repository for OpenShift Origin - the best way to build, manage, and deploy applications in the cloud. The OpenShift 3.0 codebase is based around Docker images and containers and the Kubernetes container management system.

Directories

Path Synopsis
cmd
Package cmd contains the executables for OpenShift 3.
Package cmd contains the executables for OpenShift 3.
dockerregistry
Package main contains the main executable for the integrated OpenShift Docker registry 2.0.
Package main contains the main executable for the integrated OpenShift Docker registry 2.0.
oc
openshift
Package main contains the main executable for OpenShift 3 `openshift` which is an integrated client and server binary.
Package main contains the main executable for OpenShift 3 `openshift` which is an integrated client and server binary.
Package examples contains sample applications for trying out the concepts in OpenShift 3.
Package examples contains sample applications for trying out the concepts in OpenShift 3.
pets/mysql/healthz
This is a simple health monitor for mysql.
This is a simple health monitor for mysql.
pets/peer-finder
A small utility program to lookup hostnames of endpoints in a service.
A small utility program to lookup hostnames of endpoints in a service.
images
pod
pkg
Package pkg contains all of the libraries for OpenShift 3.
Package pkg contains all of the libraries for OpenShift 3.
api
Package api includes all OpenShift-specific types used to communicate between the various parts of the OpenShift and the Kubernetes systems.
Package api includes all OpenShift-specific types used to communicate between the various parts of the OpenShift and the Kubernetes systems.
api/latest
Package latest defines the default output serializations that code should use and imports the required schemas.
Package latest defines the default output serializations that code should use and imports the required schemas.
api/v1
Package v1 is the v1 version of the API.
Package v1 is the v1 version of the API.
assets
Package assets includes all of the built static assets used by the OpenShift console and login flows, as well as all supporting server logic for running the console.
Package assets includes all of the built static assets used by the OpenShift console and login flows, as well as all supporting server logic for running the console.
auth
Package auth provides mechanisms for providing authorization and authentication to OpenShift
Package auth provides mechanisms for providing authorization and authentication to OpenShift
auth/authenticator/password/basicauthpassword
Package basicauthpassword implements authenticator.Password by making a BasicAuth call to a remote endpoint and extracting user information from a JSON response.
Package basicauthpassword implements authenticator.Password by making a BasicAuth call to a remote endpoint and extracting user information from a JSON response.
auth/authenticator/password/keystonepassword
Package keystone provide authentication via keystone.
Package keystone provide authentication via keystone.
auth/authenticator/request/x509request
Package x509request provides a request authenticator that validates and extracts user information from client certificates
Package x509request provides a request authenticator that validates and extracts user information from client certificates
auth/oauth/external
Package external implements an OAuth flow with an external identity provider
Package external implements an OAuth flow with an external identity provider
authorization/api
Package api is the internal version of the API.
Package api is the internal version of the API.
authorization/api/v1
Package v1 is the v1 version of the API.
Package v1 is the v1 version of the API.
authorization/client/clientset_generated/internalclientset
This package has the automatically generated clientset.
This package has the automatically generated clientset.
authorization/client/clientset_generated/internalclientset/fake
This package has the automatically generated fake clientset.
This package has the automatically generated fake clientset.
authorization/client/clientset_generated/internalclientset/typed/core/unversioned
This package has the automatically generated typed clients.
This package has the automatically generated typed clients.
Package fake has the automatically generated clients.
bootstrap/docker/exec
Package exec contains a utility to Docker exec into a running a container
Package exec contains a utility to Docker exec into a running a container
bootstrap/docker/host
Package host contains a utility to run commands on the Docker host by using an image in privileged mode.
Package host contains a utility to run commands on the Docker host by using an image in privileged mode.
bootstrap/docker/run
Package runner contains a utility to run Docker containers
Package runner contains a utility to run Docker containers
build
Package build contains the OpenShift build system.
Package build contains the OpenShift build system.
build/admission
Package admission contains admission control plugins that work with builds or pods that are running builds.
Package admission contains admission control plugins that work with builds or pods that are running builds.
build/admission/defaults
Package defaults contains the BuildDefaults admission control plugin.
Package defaults contains the BuildDefaults admission control plugin.
build/admission/defaults/api
Package api is the internal version of the API.
Package api is the internal version of the API.
build/admission/overrides
Package overrides contains the BuildOverrides admission control plugin.
Package overrides contains the BuildOverrides admission control plugin.
build/admission/overrides/api
Package api is the internal version of the API.
Package api is the internal version of the API.
build/api
Package api is the internal version of the API.
Package api is the internal version of the API.
build/api/v1
Package v1 is the v1 version of the API.
Package v1 is the v1 version of the API.
build/builder
Package builder contains builders for STI and Docker in OpenShift Origin
Package builder contains builders for STI and Docker in OpenShift Origin
build/builder/cmd
Package cmd contains the main entry point for the docker and STI builders
Package cmd contains the main entry point for the docker and STI builders
build/builder/cmd/dockercfg
Package dockercfg contains a command helper to read .dockercfg files
Package dockercfg contains a command helper to read .dockercfg files
build/builder/cmd/scmauth
Package scmauth provides SCM authentication methods based on secret files
Package scmauth provides SCM authentication methods based on secret files
build/client/clientset_generated/internalclientset
This package has the automatically generated clientset.
This package has the automatically generated clientset.
build/client/clientset_generated/internalclientset/fake
This package has the automatically generated fake clientset.
This package has the automatically generated fake clientset.
build/client/clientset_generated/internalclientset/typed/core/unversioned
This package has the automatically generated typed clients.
This package has the automatically generated typed clients.
build/client/clientset_generated/internalclientset/typed/core/unversioned/fake
Package fake has the automatically generated clients.
Package fake has the automatically generated clients.
build/cmd
Package cmd provides command helpers for builds
Package cmd provides command helpers for builds
build/generator
Package generator contains the code to generate Build from BuildConfig as well as REST support to help expose the generator from an API.
Package generator contains the code to generate Build from BuildConfig as well as REST support to help expose the generator from an API.
build/util
Package util contains common functions that are used by the rest of the OpenShift build system.
Package util contains common functions that are used by the rest of the OpenShift build system.
build/webhook
Package webhook contains code for managing and serving webhook services, providing post push events to trigger builds.
Package webhook contains code for managing and serving webhook services, providing post push events to trigger builds.
build/webhook/generic
Package generic contains webhook.Plugin implementation of a generic webhooks for use in testing and/or other ad/hoc usage
Package generic contains webhook.Plugin implementation of a generic webhooks for use in testing and/or other ad/hoc usage
build/webhook/github
Package github contains webhook.Plugin implementation of github webhooks according to https://developer.github.com/webhooks/
Package github contains webhook.Plugin implementation of github webhooks according to https://developer.github.com/webhooks/
cmd/admin/diagnostics
OpenShift v3 Diagnostics
OpenShift v3 Diagnostics
cmd/flagtypes
Package flagtypes provides types that implement the pflags.Value interface for converting command line flags to objects.
Package flagtypes provides types that implement the pflags.Value interface for converting command line flags to objects.
cmd/infra/builder
Package builder contains commands for running a Source-to-Images or Docker build from within a container
Package builder contains commands for running a Source-to-Images or Docker build from within a container
cmd/server/api
Package api is the internal version of the API.
Package api is the internal version of the API.
cmd/server/election
Package election provides objects for managing the list of active masters via leases.
Package election provides objects for managing the list of active masters via leases.
cmd/server/etcd
Package etcd provides objects for creating an embedded etcd server process.
Package etcd provides objects for creating an embedded etcd server process.
cmd/server/etcd/etcdserver
This is a somewhat faithful reproduction of etcdmain/etcd.go
This is a somewhat faithful reproduction of etcdmain/etcd.go
cmd/server/kubernetes
Package kubernetes provides objects for starting the Kubernetes master and node code.
Package kubernetes provides objects for starting the Kubernetes master and node code.
cmd/server/origin
Package origin provides objects for creating an OpenShift Origin server
Package origin provides objects for creating an OpenShift Origin server
cmd/util
Package util provides utility functions for the cmd packages.
Package util provides utility functions for the cmd packages.
controller
Package controller provides reusable support for controller implementations.
Package controller provides reusable support for controller implementations.
controller/shared
Package shared provides reusable support for shared informer implementations.
Package shared provides reusable support for shared informer implementations.
deploy
Package deploy contains logic for watching and synchronizing deployments from configuration.
Package deploy contains logic for watching and synchronizing deployments from configuration.
deploy/api
Package api is the internal version of the API.
Package api is the internal version of the API.
deploy/api/v1
Package v1 is the v1 version of the API.
Package v1 is the v1 version of the API.
deploy/client/clientset_generated/internalclientset
This package has the automatically generated clientset.
This package has the automatically generated clientset.
deploy/client/clientset_generated/internalclientset/fake
This package has the automatically generated fake clientset.
This package has the automatically generated fake clientset.
deploy/client/clientset_generated/internalclientset/typed/core/unversioned
This package has the automatically generated typed clients.
This package has the automatically generated typed clients.
deploy/client/clientset_generated/internalclientset/typed/core/unversioned/fake
Package fake has the automatically generated clients.
Package fake has the automatically generated clients.
deploy/cmd
Package cmd contains various interface implementations for command-line tools associated with deploymentconfigs.
Package cmd contains various interface implementations for command-line tools associated with deploymentconfigs.
deploy/controller
Package controller contains all the controllers which taken together implement the deployment system's behavior.
Package controller contains all the controllers which taken together implement the deployment system's behavior.
deploy/graph/analysis
Package analysis provides functions that analyse deployment configurations and setup markers that will be reported by oc status
Package analysis provides functions that analyse deployment configurations and setup markers that will be reported by oc status
deploy/registry/deployconfig
Package deployconfig provides Registry interface and its RESTStorage implementation for storing DeploymentConfig api objects.
Package deployconfig provides Registry interface and its RESTStorage implementation for storing DeploymentConfig api objects.
deploy/registry/deploylog
Package deploylog provides a Registry interface for retrieving deployment logs
Package deploylog provides a Registry interface for retrieving deployment logs
deploy/registry/generator
Package generator contains the code for DeploymentConfig regeneration as well as REST support to help expose the generator from an API.
Package generator contains the code for DeploymentConfig regeneration as well as REST support to help expose the generator from an API.
deploy/registry/rollback
Package rollback contains the code for generating DeploymentConfigs representing rollbacks as well as REST support for API clients.
Package rollback contains the code for generating DeploymentConfigs representing rollbacks as well as REST support for API clients.
deploy/strategy
Package strategy contains implementations of core deployment strategies.
Package strategy contains implementations of core deployment strategies.
deploy/strategy/support
Package support is a library of code useful to any strategy.
Package support is a library of code useful to any strategy.
dns
dockerregistry/server
Package server wraps repository and blob store objects of docker/distribution upstream.
Package server wraps repository and blob store objects of docker/distribution upstream.
generate/app
Package app defines reference objects used to generate OpenShift API objects
Package app defines reference objects used to generate OpenShift API objects
generate/dockerfile
Package dockerfile provides utilities for finding and parsing Dockerfiles
Package dockerfile provides utilities for finding and parsing Dockerfiles
generate/errors
Package errors defines errors thrown during config generation
Package errors defines errors thrown during config generation
generate/git
Package git allows working with Git repositories
Package git allows working with Git repositories
generate/source
Package source includes detectors for STI source repositories
Package source includes detectors for STI source repositories
gitserver
Package gitserver provides a smart Git HTTP server that can also set and remove hooks.
Package gitserver provides a smart Git HTTP server that can also set and remove hooks.
image
Package image provides support for images, image repositories, and image repository mappings, including RESTStorage implementations and registries.
Package image provides support for images, image repositories, and image repository mappings, including RESTStorage implementations and registries.
image/admission/imagepolicy/api
Package api is the internal version of the API.
Package api is the internal version of the API.
image/api
Package api is the internal version of the API.
Package api is the internal version of the API.
image/api/v1
Package v1 is the v1 version of the API.
Package v1 is the v1 version of the API.
image/client/clientset_generated/internalclientset
This package has the automatically generated clientset.
This package has the automatically generated clientset.
image/client/clientset_generated/internalclientset/fake
This package has the automatically generated fake clientset.
This package has the automatically generated fake clientset.
image/client/clientset_generated/internalclientset/typed/core/unversioned
This package has the automatically generated typed clients.
This package has the automatically generated typed clients.
image/client/clientset_generated/internalclientset/typed/core/unversioned/fake
Package fake has the automatically generated clients.
Package fake has the automatically generated clients.
oauth/api
Package api is the internal version of the API.
Package api is the internal version of the API.
oauth/api/v1
Package v1 is the v1 version of the API.
Package v1 is the v1 version of the API.
oauth/api/validation
Package validation has functions for validating the correctness of api objects and explaining what is wrong with them when they aren't valid.
Package validation has functions for validating the correctness of api objects and explaining what is wrong with them when they aren't valid.
oauth/client/clientset_generated/internalclientset
This package has the automatically generated clientset.
This package has the automatically generated clientset.
oauth/client/clientset_generated/internalclientset/fake
This package has the automatically generated fake clientset.
This package has the automatically generated fake clientset.
oauth/client/clientset_generated/internalclientset/typed/core/unversioned
This package has the automatically generated typed clients.
This package has the automatically generated typed clients.
oauth/client/clientset_generated/internalclientset/typed/core/unversioned/fake
Package fake has the automatically generated clients.
Package fake has the automatically generated clients.
oauth/osintypes
osintypes holds types that are used to interpret responses from the RangelReale osin server.
osintypes holds types that are used to interpret responses from the RangelReale osin server.
project
Package project provides support for projects including RESTStorage implementations and registries.
Package project provides support for projects including RESTStorage implementations and registries.
project/admission/requestlimit/api
Package api is the internal version of the API.
Package api is the internal version of the API.
project/api
Package api is the internal version of the API.
Package api is the internal version of the API.
project/api/v1
Package v1 is the v1 version of the API.
Package v1 is the v1 version of the API.
project/auth
Package auth provides mechanisms for enforcing authorization to Project resources in OpenShift
Package auth provides mechanisms for enforcing authorization to Project resources in OpenShift
project/client/clientset_generated/internalclientset
This package has the automatically generated clientset.
This package has the automatically generated clientset.
project/client/clientset_generated/internalclientset/fake
This package has the automatically generated fake clientset.
This package has the automatically generated fake clientset.
project/client/clientset_generated/internalclientset/typed/core/unversioned
This package has the automatically generated typed clients.
This package has the automatically generated typed clients.
project/client/clientset_generated/internalclientset/typed/core/unversioned/fake
Package fake has the automatically generated clients.
Package fake has the automatically generated clients.
quota/admission/clusterresourceoverride/api
Package api is the internal version of the API.
Package api is the internal version of the API.
quota/admission/runonceduration
Package runonceduration contains the RunOnceDuration admission control plugin.
Package runonceduration contains the RunOnceDuration admission control plugin.
quota/admission/runonceduration/api
Package api is the internal version of the API.
Package api is the internal version of the API.
quota/api
Package api is the internal version of the API.
Package api is the internal version of the API.
quota/api/v1
Package v1 is the v1 version of the API.
Package v1 is the v1 version of the API.
quota/image
Package image implements evaluators of usage for imagestreams and images.
Package image implements evaluators of usage for imagestreams and images.
route
Package route provides support for managing and watching routes.
Package route provides support for managing and watching routes.
route/allocation
Package allocation contains all the route allocation plugins.
Package allocation contains all the route allocation plugins.
route/allocation/simple
Package simple contains the SimpleAllocation route plugin.
Package simple contains the SimpleAllocation route plugin.
route/api
Package api is the internal version of the API.
Package api is the internal version of the API.
route/api/v1
Package v1 is the v1 version of the API.
Package v1 is the v1 version of the API.
route/client/clientset_generated/internalclientset
This package has the automatically generated clientset.
This package has the automatically generated clientset.
route/client/clientset_generated/internalclientset/fake
This package has the automatically generated fake clientset.
This package has the automatically generated fake clientset.
route/client/clientset_generated/internalclientset/typed/core/unversioned
This package has the automatically generated typed clients.
This package has the automatically generated typed clients.
route/client/clientset_generated/internalclientset/typed/core/unversioned/fake
Package fake has the automatically generated clients.
Package fake has the automatically generated clients.
route/controller
Package controller contains all the route handling controllers.
Package controller contains all the route handling controllers.
route/controller/allocation
Package allocation contains all the route allocation controllers.
Package allocation contains all the route allocation controllers.
route/generator
Package generator implements the Generator interface for routes
Package generator implements the Generator interface for routes
route/graph
Package graph contains graph utilities for routes
Package graph contains graph utilities for routes
route/graph/analysis
Package analysis provides functions that analyse routes and setup markers that will be reported by oc status
Package analysis provides functions that analyse routes and setup markers that will be reported by oc status
route/graph/nodes
Package nodes contains graph functions and types for routes
Package nodes contains graph functions and types for routes
router
Package router contains the abstraction for router backend implementations.
Package router contains the abstraction for router backend implementations.
router/controller
Package controller contains the router controller.
Package controller contains the router controller.
router/controller/factory
Package factory contains code used to create the router controller.
Package factory contains code used to create the router controller.
scheduler/admission/podnodeconstraints/api
Package api is the internal version of the API.
Package api is the internal version of the API.
sdn/api
Package api is the internal version of the API.
Package api is the internal version of the API.
sdn/api/v1
Package v1 is the v1 version of the API.
Package v1 is the v1 version of the API.
sdn/client/clientset_generated/internalclientset
This package has the automatically generated clientset.
This package has the automatically generated clientset.
sdn/client/clientset_generated/internalclientset/fake
This package has the automatically generated fake clientset.
This package has the automatically generated fake clientset.
sdn/client/clientset_generated/internalclientset/typed/core/unversioned
This package has the automatically generated typed clients.
This package has the automatically generated typed clients.
sdn/client/clientset_generated/internalclientset/typed/core/unversioned/fake
Package fake has the automatically generated clients.
Package fake has the automatically generated clients.
security/api
Package api is the internal version of the API.
Package api is the internal version of the API.
security/api/v1
Package v1 is the v1 version of the API.
Package v1 is the v1 version of the API.
template
Package template provides TemplateProcessor, capable of transforming Template objects into Config objects.
Package template provides TemplateProcessor, capable of transforming Template objects into Config objects.
template/api
Package api is the internal version of the API.
Package api is the internal version of the API.
template/api/v1
Package v1 is the v1 version of the API.
Package v1 is the v1 version of the API.
template/api/validation
Package validation has functions for validating the correctness of Template objects and explaining what is wrong with them when they aren't valid.
Package validation has functions for validating the correctness of Template objects and explaining what is wrong with them when they aren't valid.
template/client/clientset_generated/internalclientset
This package has the automatically generated clientset.
This package has the automatically generated clientset.
template/client/clientset_generated/internalclientset/fake
This package has the automatically generated fake clientset.
This package has the automatically generated fake clientset.
template/client/clientset_generated/internalclientset/typed/core/unversioned
This package has the automatically generated typed clients.
This package has the automatically generated typed clients.
template/client/clientset_generated/internalclientset/typed/core/unversioned/fake
Package fake has the automatically generated clients.
Package fake has the automatically generated clients.
template/generator
Package generator defines GeneratorInterface interface and implements some random value generators.
Package generator defines GeneratorInterface interface and implements some random value generators.
template/generator/examples
Package examples demonstrates possible implementation of some random value generators.
Package examples demonstrates possible implementation of some random value generators.
unidling
Package unidling supports unidling scalable resources upon network traffic to associated services
Package unidling supports unidling scalable resources upon network traffic to associated services
user/api
Package api is the internal version of the API.
Package api is the internal version of the API.
user/api/v1
Package v1 is the v1 version of the API.
Package v1 is the v1 version of the API.
user/client/clientset_generated/internalclientset
This package has the automatically generated clientset.
This package has the automatically generated clientset.
user/client/clientset_generated/internalclientset/fake
This package has the automatically generated fake clientset.
This package has the automatically generated fake clientset.
user/client/clientset_generated/internalclientset/typed/core/unversioned
This package has the automatically generated typed clients.
This package has the automatically generated typed clients.
user/client/clientset_generated/internalclientset/typed/core/unversioned/fake
Package fake has the automatically generated clients.
Package fake has the automatically generated clients.
util
Package util implements various utility functions used in both testing and implementation of OpenShift.
Package util implements various utility functions used in both testing and implementation of OpenShift.
util/docker
Package docker has utilities to work with Docker.
Package docker has utilities to work with Docker.
util/docker/dockerfile
Package dockerfile has utilities that complement Docker's official Dockerfile parser.
Package dockerfile has utilities that complement Docker's official Dockerfile parser.
util/errors
Package errors provides utility functions for various errors
Package errors provides utility functions for various errors
util/file
Package file implements utility functions used to work with arbitrary files.
Package file implements utility functions used to work with arbitrary files.
util/fsnotification
Package fsnotification provides helper functions that wrap the fsnotify filesystem notification package.
Package fsnotification provides helper functions that wrap the fsnotify filesystem notification package.
util/httpproxy
Package httpproxy contains an upgrade-aware HTTP single-host reverse proxy.
Package httpproxy contains an upgrade-aware HTTP single-host reverse proxy.
util/ipcmd
Package ipcmd provides a wrapper around the "ip" command.
Package ipcmd provides a wrapper around the "ip" command.
util/labelselector
labelselector is trim down version of k8s/pkg/labels/selector.go It only accepts exact label matches Example: "k1=v1, k2 = v2"
labelselector is trim down version of k8s/pkg/labels/selector.go It only accepts exact label matches Example: "k1=v1, k2 = v2"
util/namer
Package namer contains a name generator for unique names
Package namer contains a name generator for unique names
util/ovs
Package ovs provides a wrapper around ovs-vsctl and ovs-ofctl
Package ovs provides a wrapper around ovs-vsctl and ovs-ofctl
version
Package version supplies version information collected at build time to OpenShift and Kubernetes components.
Package version supplies version information collected at build time to OpenShift and Kubernetes components.
Package test contains cross-functional test suites for OpenShift 3.
Package test contains cross-functional test suites for OpenShift 3.
extended
Package extended contains extended tests for OpenShift Origin
Package extended contains extended tests for OpenShift Origin
integration
Package integration contains integration tests for OpenShift Origin.
Package integration contains integration tests for OpenShift Origin.
third_party
github.com/docker/libcompose/project
package project contains a stripped down version of libcompose types from commit 3ca15215f36154fbf64f15bfa305bfb0cebb6ca7
package project contains a stripped down version of libcompose types from commit 3ca15215f36154fbf64f15bfa305bfb0cebb6ca7
tools
genconversion
conversion-gen is a tool for auto-generating Conversion functions.
conversion-gen is a tool for auto-generating Conversion functions.
gendeepcopy
deepcopy-gen is a tool for auto-generating DeepCopy functions.
deepcopy-gen is a tool for auto-generating DeepCopy functions.
genprotobuf
go-to-protobuf generates a Protobuf IDL from a Go struct, respecting any existing IDL tags on the Go struct.
go-to-protobuf generates a Protobuf IDL from a Go struct, respecting any existing IDL tags on the Go struct.
genprotobuf/protoc-gen-gogo
Package main defines the protoc-gen-gogo binary we use to generate our proto go files, as well as takes dependencies on the correct gogo/protobuf packages for godeps.
Package main defines the protoc-gen-gogo binary we use to generate our proto go files, as well as takes dependencies on the correct gogo/protobuf packages for godeps.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL