v1.1.3
This is a feature and bug fix release on the Origin 1.1.x stream.
API Changes
- ImageStreamTags now return the spec tag
tag
, the current statusconditions
, and latest status generationgeneration
, so clients can get an accurate view of the current tag. - ImageStreamTags can be updated via PUT to set their spec tag in a single call.
- DeploymentConfig hooks now default the container name if there is only a single container in the deployment config.
Included projects
- Update to Kubernetes v1.2.0-dev.6 (openshift/kubernetes@9caf0a7)
- Update to etcd v2.2.4
Features
-
The administrative commands are now exposed via
oc adm
so you have access to them in a client context -oadm
will still work but will be a symlink to theoc binary
. -
IPFailover supports a router id offset, supporting multiple ipfailover setups per cluster
-
Allow the master to support recursive DNS resolution via a new master config flag
allowRecursiveQueries
, defaults to false -
The userspace node proxy can be enabled on nodes for users who want to continue using it over the iptables proxy via
proxyArguments: proxy-mode: - userspace
-
oc explain
now works for Origin types - tryoc explain dc.spec.test
-
The web console will now display more error and warning information about routes, their configuration, and their use in the system
-
Routers now report back status to the master about whether routes are accepted, rejected, or conflict with other users. The CLI will now display that error information, allowing users to know that the route isn't being served.
-
The SETUID and SETGID capabilities have been added back to the
anyuid
SCC, which ensures that programs that start as root and then drop to a lower permission level will work by default. -
Deployment hooks can now tag the most recent container image into another image stream on success - use a "test" deployment to validate the deployment succeeds, and then tag the resulting image into an image stream tag for others to use
-
Trigger a user provided command after a build succeeds but before the push - users can set
shell
(to run a shell script),command
, orargs
to run a command in the working directory of the built image. All s2i builders set the user's source repo as the working directory, so commands likebundle exec rake test
should work. -
Administrators can enforce a ratio on pod requests and limits for CPU and memory via the new ClusterResourceOverride for users on the platform.
Bugs
- Improve the web console's performance when displaying many deployments or builds
- Router unique host check should not reprocess routes that did not change
- Add the AlwaysPull admission controller to prevent users from being able to run images that others have already pulled to the node
- Fix
oc edit
when editing multiple items in a list form - The recycler for persistent volumes now uses a service account and has proper access to restricted content
- Support the block profiler in pprof
- Handle additional cGroup locations when constraining builds
- Handle scratch images from new-app
- Add support for paged LDAP queries