Conformance test suite for OpenShift
This is the public release of OpenShift Origin v3.6.0.
v3.6.0 (2017-07-30) Full Changelog
See the earlier release notes for other features implemented in this release:
In many cases, the last few lines of the build log contain an accurate reason for a failing build. This adds a new field logSnippet to the build status and populates it with the last few lines of build logs when the build is marked as failed. This field is purely informational and may not be a complete representation of the final logs.
oc cluster up dependency on oc binary #15471
ecb0f52560ac766331052a0052b1de646011247f637c15063f4d74432e1ce389 ./openshift-origin-client-tools-v3.6.0-c4dd4cf-linux-64bit.tar.gz
c9565850257fd758585118c4b5e1be42ddcf133026c02adee2695191690f022e ./openshift-origin-server-v3.6.0-c4dd4cf-linux-64bit.tar.gz
320dd318b4b094fea9aadee9473173054d1f11b97895b94315fe2f095f08b652 ./CHECKSUM
6ade4ce9b300b1a9ed4ccfa49f3476a0721c71b78e7dd43ca58f4752b29ab5f1 ./openshift-origin-client-tools-v3.6.0-c4dd4cf-mac.zip
6a45e7fe115dd4c8675ba06e8d958da6819b84a876ea6eb1c085a92b741e43f7 ./openshift-origin-client-tools-v3.6.0-c4dd4cf-windows.zip
This is the first release candidate for OpenShift 3.6.
volumes array will now default to ["none"]
spec.tls.destinationCACertificate fields
/oapi/v1/routes/* endpoint it will have a synthetic certificate injected. Retrieving the route from the new /apis/route.openshift.io/v1 endpoint will show the new empty value./apis/build.openshift.io/v1 endpoint pruning will be automatically defaulted
v3.6.0-rc.0 (2017-07-13) Full Changelog
API aggregation is a key Kubernetes feature that will make it easier to extend Kubernetes clusters. The 3.6 release enables aggregation as tech preview and includes the Kubernetes 1.7 APIs. Its primary purpose in 3.6 is to support the service catalog.
httpd images and quickstartThe httpd image makes it easy to serve content to users, proxy, or extend with custom support for Apache modules. This image is added to the default image streams along with a quickstart template.
Now that a significant fraction of all users have access to Docker 1.10, enable schema2 support in the registry by default. This will allow Docker 1.10+ engines to push images using the new schema and sets the stage for future improvements in images.
oc cluster upThe --service-catalog flag on oc cluster up will deploy the new service catalog and configure the instance
with support for the template broker and the new service catalog UI. This feature is tech preview in OpenShift 3.6.
Kubernetes objects like Deployments and StatefulSets can now add an alpha annotation to request image stream resolution from any image field in their pod specs. If an image stream tag with matching name and tag exist, the value of the image will be replaced with the latest tag in that stream. Use oc set image-lookup to configure the flag.
valueFrom field to inject dynamic values into environment or labelsBuilds, like pods, can use the valueFrom field on each label or environment variable to leverage data from the parent build. This allows some limited dynamic properties to be set into each build result.
oadm manage-node to support multiple output formats #14655
oadm migrate storage was double counting when filtering #14724
oadm migrate was double printing early exit error #15000
--api-version field back to oc explain for cross version output #14872
--api-version #14919
oc set triggers is displaying listed resources twice #14987
git ls-remote in new-app when checking remote registry #14758
oc new-app --build-env doesn't work on templates #14922
oc new-app displays correct error on missing context directory #14715
oadm migrate authorization to allow manual migration #14429
oadm migrate etcd-ttl which encodes upstream TTL migration #14559
oadm migrate volumesource to detect deprecated fields #14810
projectName references #1702
$evalAsync block #1830
apps group #1839
553ce3edcfe4e0a5ec787fa7697713ff7c8cb49aa08d680e446eb8c02d786a1e ./CHECKSUM
5808b3d29c72d04643c98ee1f51611222fa4c14fe420632d60812dc9b59755fd ./openshift-origin-client-tools-v3.6.0-rc.0-98b3d56-linux-64bit.tar.gz
94b7c89ed9e177a31713392fcaf815c029c2bf8b7689d3a2b316a678cb990a34 ./openshift-origin-server-v3.6.0-rc.0-98b3d56-linux-64bit.tar.gz
454970d47bc4fef39e0835bd1a8806f6966f41515a5da269c15b871f98368263 ./openshift-origin-client-tools-v3.6.0-rc.0-98b3d56-mac.zip
11a8a94f96be56a66c73cb1ee6ed9365307c40136c5ea80beb4deeefb2ee1b23 ./openshift-origin-client-tools-v3.6.0-rc.0-98b3d56-windows.zip
This is a feature release of OpenShift Origin.
oc import docker-compose has been removed #13795
status.unavailableReplicas field on deployment configs no longer accepts negative numbers #14046
v3.6.0-alpha.2 (2017-06-07) Full Changelog
spec.tls.destinationCACertificate field on a route is now optional - routers that don't allow defaulting will reject this routeauto_unmount mount option for glusterfs fuse mount. #14443
Cluster workload federation is nearing beta status in Kubernetes and is now part of the OpenShift distribution. The kubefed binary is built as part of Origin and will help stand up a tech preview cluster.
The cluster capacity command emulates the Kubernetes scheduler for a set of pod workloads and estimates how many pods can be scheduled on a cluster.
The garbage collection feature in Kubernetes is now stable and enabled in OpenShift. OpenShift controllers like deployment configs, build configs, and templates set owner references on the objects they create, which means deleting a deployment config will now automatically clean up the replication controllers and pods created by the deployment. The web console uses owner information to better organize resources and can now delete resources when they have changed. See the documentation for more on how to leverage garbage collection to manage cleanup.
This release improves egress network policy (handled by an egress router) to make managing traffic leaving namespaces easier via DNS name support on destinations and also targeting multiple destinations.
Git branches and tags are both represented as "references" inside of a repository. GitHub adds references in Git for each pull request, but to use that reference in an OpenShift build we must first fetch the
information from the remote server. The ref field on a build's Git source specification can now point
to any valid Git reference and OpenShift will attempt to retrieve that ref, allowing pull requests to
be spawned for a specific build.
ref field on builds to point to any Git reference #13893
OpenShift image streams make it easy to decouple image management from deployment. Image streams can now be used directly from Kubernetes resources like StatefulSets, Jobs, CronJobs, Deployments, or DaemonSets via the new lookupPolicy that has been added to image streams. The oc set image-lookup command allows you to mark an image stream within your project as being a local reference:
$ oc import-image mysql:latest
$ oc set image-lookup mysql
Now you can reference the image mysql:latest from within a Kubernetes controller and the corresponding image stream tag will be used:
$ oc run --image=mysql:latest --restart=OnFailure myjob
$ oc get pods
The pod created by the job will use the image tagged as latest in the image stream mysql. Builds, pods, jobs, replicasets, and replication controllers will all respect these settings, and administrators can configure their image policy to add new resources.
The image trigger controller has been upgraded and now supports updating deployments, stateful sets, daemon sets, and cron jobs whenever an image stream tag is updated. A new alpha annotation can be set on the resource to describe which image stream tag should cause an update.
To update a DaemonSet whenever the image stream tag 'image:latest' in namespace 'namespace1' changes, run:
$ oc set triggers daemonset/monitoring --from-image=namespace1/image:latest -c main
You can remove a trigger by adding the --remove flag. This allows you to run an OpenShift build
or run a scheduled import to keep your applications up to date..
Trigger updates are alpha in 3.6.0.
Build configs now support two parameters to control how many successful and failed builds are retained. By default, no limit is set and all builds are retained. The fields are spec.failedBuildsHistoryLimit and spec.successfulBuildsHistoryLimit.
The v3.6.0 release integrates a large number of changes the OpenShift team has contributed to Kubernetes around security, authorization, RBAC, and core code refactoring. While this will continue for several releases, the OpenShift and Kubernetes RBAC resources are being aligned and the primary API going forward for RBAC will be the Kubernetes version. The existing APIs will remain, especially those that expose features not yet supported in Kubernetes like scoped tokens.
Starting in this release, all OpenShift RBAC resources are automatically migrated to Kubernetes RBAC resources. Users should not see any change in behavior while these migrations occur.
Future releases will include migrating from SecurityContextConstraints to PodSecurityPolicy as well naming and policy updates to system managed policies.
The service serving certificate feature makes it easy to generate a valid TLS server certificate for your applications for securely serving HTTPS within a cluster. The router is now enabled to automatically reencrypt traffic to services that use these certificates for routes that specify a blank spec.tls.destinationCACertificate field. When a cluster is configured with a default wildcard certificate, this means that you can deploy applications to OpenShift that are secured end to end without having to generate or manage your own certificates.
See the Prometheus example
for this in action. The service requests generation of a secret prometheus-tls containing a TLS serving certificate for prometheus.NAMESPACE.svc, and the route points to the service with the TLS type Reencrypt, but without a destinationCACertificate. The router will automatically fill in the service-ca.crt file, which is available in every pod.
OpenShift has natively supported detached signing certificates on images for several releases, and this release adds a new CLI command to make it easy for an administrator to verify the signatures on images manually or as part of an automated image publish flow. This allows the web UI and CLI to show information to the end user about the state of the signature.
See oc adm verify-image-signature for more.
build: Display jenkins url for pipeline build #13979
registry: Add prometheus metrics for dockerregistry #12711
route: Sanitize certificates from routes in the router #13897
storage: iSCSI CHAP support #14112
route: Allow controlling spec.host via a new permission #13905
prometheus: Make the Prometheus example a fully automated secure deployment #13782
ha: Enable leader election on endpoints for controllers #14094
router: Add defaults and env control of the fin timeouts in the router #14220
router: Make HAProxy's log format configurable #13029
sdn: Add an OPENSHIFT-ADMIN-OUTPUT-RULES chain for admins to use #14221
server: Prepare for API aggregation by supporting the new Kube aggregation endpoint #14285
router: Shuffle endpoints for routes #14008
web: Update overview to use toast notifications #1654
web: Add landing page tour #1508
web: Support filtering provisioned services on overview #1444
web: Only show service catalog resources when available #1573
web: disambiguate kinds on other resources by showing group #1478
web: Bug 1447997 - Show warning for unsupported resource versions #1512
web: Update the Other Resources Page to only show resources supporting the 'List' verb #1572
request-timeout val to oc login restclient #12062
oc set commands support --dry-run and --local #14123
oc adm manage-node --list-pods #12528
oc status should display services of type ExternalName correctly #14448
oc deploy #14019
9cc44e7890b39953303ad18f2187a6aac82cd3a6fe570b9432c47df982589075 openshift-origin-client-tools-v3.6.0-alpha.2-3c221d5-linux-64bit.tar.gz
a99e5f070d926ac996acf2db11f518463b661703b4712e5fca6a1f8d9504d2af openshift-origin-client-tools-v3.6.0-alpha.2-3c221d5-mac.zip
b88c724fb6c54b12ffde296c736c2190a0459c52b6f6067552efccbe648f6694 openshift-origin-client-tools-v3.6.0-alpha.2-3c221d5-windows.zip
42a56ee6f66e39815874c8e03c1cee373e20ff3f1fd83c5829df043c8988ba0d openshift-origin-server-v3.6.0-alpha.2-3c221d5-linux-64bit.tar.gz
This is a patch release of OpenShift Origin.
v1.5.1 (2017-05-16) Full Changelog
7d683132a1ea27806d7b2dfbeec4dd1b9d5b0b7db6b97ed05506365135453f55 openshift-origin-client-tools-v1.5.1-7b451fc-linux-32bit.tar.gz
1e5f73098c3e3bf6f887c8678c078f650e62c477eca255c0f131d6b6be805c6c openshift-origin-client-tools-v1.5.1-7b451fc-linux-64bit.tar.gz
0cc3646f2cb2aafcde4bc5bc6890f1c78dabcda4b90ac0b891edef7d7b86bdfe openshift-origin-client-tools-v1.5.1-7b451fc-mac.zip
06f320daef3539f0d7e4a526ec2cbdfdfbfa3a61022ca6fdc0ebcb1ed09ad3f7 openshift-origin-client-tools-v1.5.1-7b451fc-windows.zip
abe50d51aa2485cac9374026a46c30901335f86171d79b7a5747f289e26f9cd0 openshift-origin-server-v1.5.1-7b451fc-linux-64bit.tar.gz
This is the release of OpenShift Origin 1.5.
v1.5.0 (2017-04-21) Full Changelog
7100e3c9324ddb31cd0bee1c0bc74d11f79aa580f7c8776eba321094029503ab openshift-origin-client-tools-v1.5.0-031cbe4-linux-32bit.tar.gz
e928067175be0e8a5947c21ebbbf1359687846749e83411b7cd0b99759968605 openshift-origin-client-tools-v1.5.0-031cbe4-linux-64bit.tar.gz
8ea85801afbd464a1bb90346e31c3f3a3325ae93fc188c0d34bd49fc68fc7e16 openshift-origin-client-tools-v1.5.0-031cbe4-mac.zip
e4650d9a53678141c17147a98670fc842fc78049762877def4cb66e385aadee7 openshift-origin-client-tools-v1.5.0-031cbe4-windows.zip
e9bd3c92842acb17ab920b663dfb80f094707fbac8a92dde341631dbfdb13628 openshift-origin-server-v1.5.0-031cbe4-linux-64bit.tar.gz
This is a feature release of OpenShift Origin.
v3.6.0-alpha.1 (2017-04-12) Full Changelog
attributeRestrictions field in subject access reviews is deprecated and will be removed in a future release, to be consistent with the new approach of having multiple resource types for access reviews. #13466
Templates allow users in OpenShift to easily define, share, and deploy precanned applications. The new service broker will allow any template to be exposed in the service catalog and then consumed by end users. The broker will initially support deploying the template inside of the user's project, but eventually allow templates to be used to deployed on other clusters and linked back to the end user.
To support the service broker, a new resource has been added to projects - the TemplateInstance. This lets you declaratively instantiate a template and then in the future update that template.
Template service broker is tech preview for OpenShift 3.6
The router has been upgraded to return Prometheus metrics for routes and the pods under those routes. New clusters will have the ROUTER_METRICS_TYPE environment variable set to haproxy and ROUTER_LISTEN_ADDR set to 0.0.0.0:1935, which turns on metrics on port 1935 (protected by the ROUTER_STATS_PASSWORD and user).
The exposed metrics describe per route, service, and pod information about the traffic flowing over the routers, and can be gathered by an Prometheus capable collector to report information about edge traffic.
F5 BigIP servers allow for multiple active "partitions" to be managed for security and failure separation at the API level. This change adds support for targeting a partition from the F5 router management code and makes it possible for OpenShift to manage only a subset of a given F5 router.
Like the GitHub and generic web hooks, this allows users to create a webhook trigger with oc set triggers and then use that webhook from
a GitLab or BitBucket repository. The hook supports extracting the commit message and author and adding it to the trigger cause.
A new configuration flag has been added to the OpenShift config that limits which registries users can import images from by default. Administrators who can create images directly via the API can import any image, but regular users will receive an error if they import from an unsupported registry.
By default, the list of registries is set to the important publicly hosted registries.
A new event is sent when a build starts running, and when it succeeds, fails, or is cancelled another event will be reported. This makes it easier to see the timeline of events in the CLI and web console.
The service catalog is an important new component of OpenShift and Kubernetes and will be tech preview in 3.6. The web console will expose binding services provisioned in the catalog to existing applications, as well as deploying new components into a project from the console (via the template broker). More coming soon!
oc tag should not allow setting an alias tag across different image streams #13632
oc cluster up #13636
oc adm registry #12951
38378daa2945bbba332c1af2d857ff09fded70420ee742d72a704fdd4d242043 openshift-origin-client-tools-v3.6.0-alpha.1-46942ad-linux-64bit.tar.gz
ea35585dcdd3719555396f2e58141cd68ba1a94c033b1bc89d72c4347b543267 openshift-origin-client-tools-v3.6.0-alpha.1-46942ad-mac.zip
a336cc57f1aad5c88cd5c453e9068831e00d6d052c9ace59770bdabd39413ba4 openshift-origin-client-tools-v3.6.0-alpha.1-46942ad-windows.zip
ac72399befd3a7f147d09d556853f6871a9a78bec0eb63f9a5e56fb01a094eb3 openshift-origin-server-v3.6.0-alpha.1-46942ad-linux-64bit.tar.gz
This is a feature release towards OpenShift 3.6.
Please note that we have updated the version numbering scheme for OpenShift to be consistent with the OpenShift version history to minimize impact to the installer and other related documentation and web links. OpenShift 3.6 replaces version number 1.6, and will be based on Kubernetes 1.6.
v3.6.0-alpha.0 (2017-03-21) Full Changelog
API groups in Kubernetes allow extension of core APIs and better separation of unrelated API types.
In this release we are introducing API groups for all OpenShift API resources so that in the future
they can be used as extensions to a base Kubernetes distribution. These resources continue to be available
at /oapi/v1, but clients should begin using the new paths.
New API groups are available from the OpenShift API server at:
/apis/apps.openshift.io/v1: DeploymentConfigs/apis/authorization.openshift.io/v1: OpenShift role based access control/apis/build.openshift.io/v1: Build configs and builds/apis/image.openshift.io/v1: Images, ImageStreams, and other supporting resources/apis/oauth.openshift.io/v1: OpenShift OAuth resources like ClientAuthorization and Tokens/apis/network.openshift.io/v1: Network policy for openshift-sdn and NetworkEgressPolicy/apis/project.openshift.io/v1: Projects and project requests for role based access to namespaces/apis/quota.openshift.io/v1: ClusterQuota and supporting namespaced resources/apis/route.openshift.io/v1: Routes/apis/security.openshift.io/v1: PodSecurityPolicyReview resources/apis/template.openshift.io/v1: Templates/apis/user.openshift.io/v1: User and group resourcesStored templates, configuration, and client code intended for use with 3.6 and above can substitute the
apiVersion field for an object with GROUP/v1. CLI code will continue to generate objects with the
legacy apiVersion v1 to enable working with older versions. On many commands you can use
--output-version to indicate the new version
The web console has been heavily revised with a focus on showing the relationships between services and deployments, with significant enhancements to layout and information presentation.
Other changes:
This makes it easier to parameterize these two classes of builds
reference-policy on oc import-image #13339
timeout http-keep-alive when timeout http-request is used to prevent short sessions #13051
7a353841eb0edd28f0a4ab86279e79992804456a95f53125bdffae4daf8a5090 openshift-origin-client-tools-v3.6.0-alpha.0-0343989-linux-32bit.tar.gz
60e2cc967086acbba0fee1e6c98ed5792bde5af80d64ddaaa6727e835848d421 openshift-origin-client-tools-v3.6.0-alpha.0-0343989-linux-64bit.tar.gz
4583a8dfebd04d7d193f635629dd03113c0ba199f1b14c945928274982540bfb openshift-origin-client-tools-v3.6.0-alpha.0-0343989-mac.zip
f38b393e7bdcf8f11077ce04c931b274a4c83ccb53513fd7cb14e1f0b575436f openshift-origin-client-tools-v3.6.0-alpha.0-0343989-windows.zip
6607b727d3db21fa211240a41bd399573018bc76e54f265ba9d5632add9ba87a openshift-origin-server-v3.6.0-alpha.0-0343989-linux-64bit.tar.gz
This is the first release candidate for OpenShift Origin v1.5.
Roadmap for the v1.5.0 release
v1.5.0-rc.0 (2017-03-09) Full Changelog
f8e1b6da0fe766a203f9cc454608eaa17eadf64da623466f1d8e1c39e2639997 openshift-origin-client-tools-v1.5.0-rc.0-49a4a7a-linux-32bit.tar.gz
1796f5131d253591c4649ee316b0f6d7a0b48b70010c56b0c0017e081475d284 openshift-origin-client-tools-v1.5.0-rc.0-49a4a7a-linux-64bit.tar.gz
60c8c174a6078382cd347dd75f8a4d362c19d5b2c9cc0e21baf6f86a6a56b6f3 openshift-origin-client-tools-v1.5.0-rc.0-49a4a7a-mac.zip
5d257629dc09ebd6e674ac7cb719ef423ec2d6ae6c237e251c8fa68160102ec5 openshift-origin-client-tools-v1.5.0-rc.0-49a4a7a-windows.zip
5c3475fa31d278efbb6a3f350eefd15d0ce2cb938043d11ac3c673250d9b39ab openshift-origin-server-v1.5.0-rc.0-49a4a7a-linux-64bit.tar.gz
This is a development release of OpenShift Origin towards v1.5.0.
--credentials flag is now removed from oadm router and oadm registry #10830
groups field on the User object has been deprecated #12870
Group object and reference the user by name.v1.5.0-alpha.3 (2017-02-19) Full Changelog
If you specify a parameter replacement in the namespace field of a template object, it will be preserved:
kind: Template
apiVersion: v1
parameters:
- name: NAMESPACE
objects:
- kind: Service
metadata:
namespace: foo # ignored
- kind: PersistentVolumeClaim
metadata:
namespace: "${NAMESPACE}" # will be set to the value of NAMESPACE
Static values for namespace will continue to be ignored to prevent breaking old templates that included those fields
clusterid, an optional parameter to storageclass. #12556
The OpenShift 1.5 release added a few new features for templates, including the ability to have integer, boolean, array, or map inputs (using the ${{PARAMETER}} syntax). This alpha also allows templates to span namespaces if you parameterize the namespace field of your objects. Previously, all namespace fields were stripped, but a template object with a namespace that references a parameter will now be filled in, allowing you to instantiate cluster scoped resources that refer to a named resource in the template. oc process --local has been added to allow you to locally transform a template for use with a regular Kubernetes server - the transformation is performed on the client instead of requesting the server do the transformation.
--local #12996
The HAProxy router can be configured to expose Kubernetes Ingress objects. This feature is still under development and may change as more security protections are put into place. Not all features supported by Routes are available, including some advanced annotations.
Multicast and NetworkPolicy support are now available in OpenShift SDN for testing. Please see the documentation for more info on how to enable them.
For the last several releases Kubernetes and OpenShift have been preparing to allow nodes to "self-register" in cloud environments where nodes can be spun up or down dynamically. In the v1.5.0 release the new experimental --bootstrap flag is available on nodes and will have the node request a client certificate from the master, then request a serving certificate, then download its node configuration from a config map. Cloud VM images can be "baked" with an account capable of self registration and the new oc adm certificate approve command can be used to approve the client and serving certificate requests.
This feature is still experimental and may change in future releases.
oc cluster up now installs a Prometheus and Heapster template to the kube-system namespace - as an administrator you can switch to that namespace and easily install them for monitoring your cluster.
Prometheus can monitor your nodes, apiserver, and services labelled with the appropriate annotations and record metrics or fire alerts. Launch and expose Prometheus with:
$ oc project kube-system
$ oc new-app prometheus
$ oc expose svc/prometheus
See the Prometheus website for more info.
To use a standalone Heapster instance with no historical metrics, run:
$ oc project kube-system
$ oc new-app heapster-standalone
Autoscaling should now be enabled for your cluster. This is useful for smaller clusters where you don't need historical data as provided by Hawkular.
kube-system namespace on cluster up #12844
In order to make it easier to capture profiles and other debug information about a running cluster, the /debug/pprof endpoints are
exposed on apiservers, controllers, and nodes, but protected via a new cluster-debugger role. Since the debug endpoint can extract sensitive information from the cluster, you should only give that role to trusted actors.
# Retrieve and process a heap dump from the master as a cluster-debugger
$ oc get --raw /debug/pprof/heap > /tmp/heap
$ go tool pprof PATH_TO_OPENSHIFT_BINARY /tmp/heap
# Capture a 30s CPU profile from the master as a cluster-debugger
$ oc get --raw /debug/pprof/profile > /tmp/cpuprofile
$ go tool pprof PATH_TO_OPENSHIFT_BINARY /tmp/cpuprofile
oc create route and a column for the wildcardpolicy to `oc get route' #12713
dc --dry-run to rollout undo #12729
-z on oadm policy add-cluster-role-to-user #12902
oc debug #12585
oc idle #12718
oc status #12328
oc edit istag/NAME #12731
oc tag --reference-policy to control whether pullthrough images are resolved to local tags #12862
insecureEdgeTerminationPolicy is Allow #12802
kubernetes.io/description on storage classes #1147
input-group class when hiding copy to clipboard button #1211
k in usageValue filter #1249
ba77489cfaba0b699aae4145a934bd974f3370de33698452f9b167bfadd0d798 openshift-origin-client-tools-v1.5.0-alpha.3-cf7e336-linux-32bit.tar.gz
cd126aee3a2ed9734724b483adb4256035c8de840ae409f11adbafa0ec3d2042 openshift-origin-client-tools-v1.5.0-alpha.3-cf7e336-linux-64bit.tar.gz
36e03331b2d434ebc26a4004080fb07d14308f7f2af619ff9eb366120dfbc58e openshift-origin-client-tools-v1.5.0-alpha.3-cf7e336-mac.zip
0bf59816e8a1c235bc76f443961fb4d6ef387432005ecea139684ed9b69b90c3 openshift-origin-client-tools-v1.5.0-alpha.3-cf7e336-windows.zip
4c67e4bb982ab3fa80f85fb26f2b0f6a1e4c728cc62ee12dd25f4065a81131fc openshift-origin-server-v1.5.0-alpha.3-cf7e336-linux-64bit.tar.gz