v1.0.4
Upgrading:
- To make it easier to upgrade, the
oadm reconcile-cluster-roles
command has been added to update your cluster roles to match the internal default. Use this command to verify the cluster infrastructure users have the appropriate permissions.
Features:
-
Split the
oc
binary from the OpenShift binary - now much smaller (40m!) -
Display the current version on startup of the master, cleanup some startup logging
-
Rolling updates can now be done by percentage - you can specify the percentage of pods to update by a negative or positive amount that adjusts the amount of replicas in chunks. If negative, old deployments will be scaled down first - if positive, extra pods are created first. The rolling update will work to keep the desired amount of pods running (100% of the old deployment size when a positive percentage, or 100%-UpdatePercent when negative) as it goes
-
Even more information available in
oc status
- make it easier to see the types of resources that are being represented by the output -
Search for images, templates, and other inputs for
oc new-app
with the--search
and--list
flags. To find out what is available, run:$ oc new-app --search php
which will show you all of the images or templates that include PHP
-
oc new-app
will now always add anapp=<name>
label on the created resources when you don't specify labels with--labels
. The name is inferred from--name
, or the name of the first component passed to the command (for instance,oc new-app php
will add a labelapp=php
to all of the resources it creates). You can then easily delete all of those components usingoc delete all -l app=php
. -
The ability to use host ports and the
hostNetwork
option is now properly secured by security context constraints, and only restricted or higher users can use them. -
The
RunAsNonRoot
option for pod security constraints has been added - it is now possible to restrict users to running pods that are non-root (have an explicit USER numeric value set in their Docker image, or have specified the user id on their pod security context) -
Add an
oc rsh POD
command that is a shortcut foroc exec -itp POD -- bash
to make it easier to get a remote shell into your pods.
Fixes:
- Routes should default to using the route name when creating a virtual host, not the service name
- The
oc expose
command should not default to creating routes except when a service is exposed - More detail shown on image streams page in the web console
- Display source code revision info in the build describe output
- Display TLS termination output in route describe output
- Allow image import to work with registries that don't implement the whole Docker Registry API (Pulp read only registries)
- Deployment configs should trigger deployment when the
metadata
field of the pod template is changed, not just when thespec
is changed. - When using
oc new-app --name=foo
, the--name
argument should also change the name of the image stream - The project request template should allow Kubernetes resources as well as OpenShift resources
- Allow
oc volume
to change the volume type when the mount-path is unambiguous - Builds now properly cancel when the user requests them, rather than running to completion.
- Master startup no longer has a chance to generate certs with duplicate serial numbers (rendering them unusable)
oc new-app
will now properly set the labels passed with--labels
onto the pod template and selector for the deploymentoc export
should no longer fail when exporting image streams that have no tags under theirspec