- We now release package metadata with the fabric8-platform so that we can use the gofabric8 tool to upgrade and downgrade releases easily via
gofabric8 upgrade
along withgofabric8 packages
andgofabric8 package-versions
- Jenkins Pipelines now use ImageStreams when deploying to different environments on OpenShift
- Jenkins master will run as a non privileged container
- Jenkins pipelines will now detect if running on OpenShift for non java application pipelines and avoid mounting the docker socket in build pods, handing off to OpenShift binary source to build docker images.
- Pipeline start time improvements
- fix to fabric8-maven-plugin to avoid chmod'ing non persistent volume mounts fabric8io/fabric8-maven-plugin#772
This release fixes a number of gremlins using fabric8 with kubernetes 1.5.x and the latest minikube
- to make it easier to keep track of which fabric8 platform release version you are using gofabric8 now clearly outputs the platform version when you install fabric8
- we now default to use the internal git URL for gogs repositories (http://gogs/...) when creating projects and building them. This works around all kinds of DNS issues folks have seen; particularly when using the public cloud since the pods inside kubernetes now no longer need to be able to see the public DNS names to navigate into gogs.
- support for installing, upgrading and removing fabric8 via helm
- on kubernetes we now support specifying a branch on the build settings form
- Upgrade to Jenkins2.x alpine base image
- Include the very cool Jenkins Blue Ocean
- Use the new @Library to import fabric8 Jenkins CPS Shared library in Jenkinsfiles
- Add experimental Keycloak app
- Upgrade experimental Taiga 3.0.0 and add persistence
- Define multiple containers to include in a build pod from a Jenkinsfile. Excellent blog by Ioannis
- Adds support for persistence to various apps (gogs, nexus, jenkins). To create persistent volumes or opt out of persistence check the persistence guide
- Includes documentation on how to create Spring Boot microservices on kubernetes with fabric8
- We now use the exposecontroller to decide whether to create Ingress resources on Kubernetes, Route resources on OpenShift, use external IPs via LoadBalancer types on public cloud or use nodePorts on local single node installations.
- All quickstarts and archetypes have moved to the new 3.x version of the fabric8 maven plugin
-
Fabric8 DevOps has new chat based workflow steps for notification and approval of Jenkins Workflow based Continuous Deployment pipelines inside the chat application like Lets Chat or Slack. Here's an example so you can see how it looks using the Fabric8 DevOps library of reusable Jenkins Workflows
-
All generated Kuberentes integration tests are now invoked by default in the Fabric8 DevOps reusable Jenkins Workflows
-
Fixes these 10 issues
-
Note we highly recommend all fabric8 users to upgrade to this release ASAP. This release fixes a bug which showed up in recent versions of Chrome where we used the wrong URL during OpenShift OAuth login causing folks not to be able to login with the console unless explicitly trusting the certificate.
- This release fixes some regressions found in OpenShift 1.0.2 or later when using Continuous Deliver with Fabric8 DevOps
- Adds nicer links to Continuous Deployment environments in the console
- Fixes these 2 issues
- Upgraded to the latest kubernetes 1.0 schema. This version now works on OpenShift Origin 1.0.2 or later
- Fully working Canary release, stage, approve and promote builds in the Jenkins Workflow when using Continuous Deliver with Fabric8 DevOps
- Fixes these 5 issues
- This release now means that the fabric8 console works great on vanilla kubernetes and GKE as well as OpenShift. Check out this demo video to see it on GKE
- The mvn fabric8:apply goal now works out of the box on both vanilla Kubernetes and OpenShift without you having to configure any properties
- A new mvn fabric8:recreate goal for less typing if you want to ensure all resources are created or recreated
- Fixes these 18 issues
- first release of the new Jenkins Docker Workflow based Continuus Integration / Continuous Delivery system
- integrated support for the fabric8-devops-connector to connect various DevOps services like git hosting, chat, issue tracking and jenkins for a project reusing the optional
fabric8.yml
file via JBoss Forge, Maven or in a JVM. - The
fabric8:create-build-config
goal is now renamed tofabric8:devops
to reflect the more generic nature of updating the DevOps configuration via the fabric8-devops-connector - Fixes these 16 issues
- The new project wizard now lets you configure a fabric8.yml file like this example for configuring the devops side of a project such as the chat room and issue tracker for a project and whether code review is enabled. Over time when we move to the Jenkins Docker Workflow for builds; we'll be able to use configured the flow too.
- Fixes these 13 issues
- The Metrics and Logging now work out of the box if you run them by pressing the
Run...
button on theApps
tab in the console when using the vagrant image - The Chat now works out of the box without having to manually figure out rooms and tokens and pass them on the command line so that Hubot can connect to Let's Chat
- Fixes these 3 issues
- New getting started guide based on a new easier to use vagrant image
- The vagrant domain is now
vagrant.f8
getting ready for DNS support inside the vagrant image - You can now easily run the fabric8 apps from the
Run...
button on the console - Fixes these 39 issues
- Updates to the
v1
schema version in kubernetes - The fabric8 vagrant image has moved into the fabric8-installer repository
- Fixes these 15 issues
- Fixes these 3 issues
- Fixes these 8 issues
- Fixes these 39 issues
- Improved user guide which is hopefully more clear along with instructions on how to Install Fabric8 on OpenShift V3
- migrates to the v1beta3 version of the Kubernetes schema by default including much better validation
- Fabric8 Apps are now easier to install on an existing Kubernetes or OpenShift environment via a OpenShift templates JSON file.
- Maven fabric8:json goal now supports the generation of OpenShift templates
- Maven fabric8:apply goal is the new name of the old
fabric8:run
goal to better describe applying JSON to a kubernetes environment and creating/updating/deleting resources. - New maven fabric8:create-routes to lazily create any missing OpenShift Routes
- The fabric8 console is now more reactive thanks to the support of websockets for real time updates
- First spike of Fabric8 Continuous Delivery making it easier to build, release and provision software faster and more reliably
- Fixes these 49 issues
- Fixes these 5 issues
- Fixes these 2 issues
- Includes Chat support via hubot for notifying chat rooms in IRC, Slack, HipChat or Campfire on build completion or failure etc.
- Fixes these 5 issues
- Fixes these 20 issues
- Fixes these 60 issues
- Migrated to hawtio 2.x for the console making it small and lightweight with optional modular services
- Added the App Library to provide a configurable library of Apps you can easily run and install or uninstall; rather like your library of Apps on a mobile device.
- Fixes these 18 issues
- Fixes these 5 issues
- Handle the new HTTPS only REST API in Kubernetes / OpenShift
- Fixes these issues
- Uses auto-generated JSON Schema from the OpenShift/Kubernetes go source code to provide faithful Jackson DTOs for the REST API against v1beta2 of the kubernetes/openshift APIs
- Improved App tab in the console showing a nicer detailed view of apps/pods
- Fixes these issues
- Fixes these issues
- Fixes these issues
- Fixes these issues
- Fixes these issues
- Added a quickstart for camel-sql which uses the Camel REST API and shows up in the API Registry / API console
- Fixes these issues
- Much nicer console which now has
- deep linking of Pods to Kibana logs if kibana is running
- allows you to view the number of pods and their status on the Controllers and Services pages
- links on the Controllers and Services pages to the pods running for a single Controller or Service
- Fixes these issues
- Fixes these 12 issues
- Ported the API console to work on Kubernetes so that the APIs tab appears on the Fabric8 Console if you run hawtio inside Kubernetes and are running the API Registry service
- Adds Service wiring for Kubernetes so that its easy to dynamically link nav bars, buttons and menus to remote services running inside Kubernetes (e.g. to link nicely to Kibana, Grafana etc).
- Fixes these 10 issues
- Fixes these 5 issues
- Fixes these 4 issues
- Fixes this issue
- Fixes these issues
- Nicer layouts and icons in the Console (and the Wiki tab is now called Library as in an Application Library)
- Fixes these 5 issues
- Improve the appearance of App Zips when deployed (or dragged and dropped) into the Console Wiki tab
- Fixes these 5 issues
- First release of the Kubernetes based Fabric8 which reuses the standard Kubernetes REST APIs for container orchestration and either Docker container images or Jube image zips for container provisioning.
- Fixes these 8 issues
- Profile name must be in lower-case letters
- Improves startup experience so its a bit more clear when fabric8 has completed provisioning.
- Improvements to the REST API so you can easily view containers for a profile, start/stop/delete containers or POST new profiles to a version or DELETE profiles
- Fixes these 60 issues
Note that until we move to CXF 3.x the REST API is at http://localhost:8181/cxf/fabric8 and not its usual http://localhost:8181/api/fabric8 - you can always use the fabric:info CLI command to find it.
- Fixes running fabric8 inside docker and creating containers from within docker
- Fixes these 12 issues
- Upgrade to Apache Karaf 2.4.x build so that we get full Role Based Access Control (RBAC) support on all MBeans, OSGi services and CLI commands (hence the upgrade to 1.2.x as the change to RBAC was bigger than a minor fix to 1.1.x)
- Container names must be lower case only
- Improved Auto Scaling UI for easier configuration of the Auto Scaling Requirements
- Improved Configuration tab on the Profile page in the web console so its easier to configure all profiles whether containers are running or not and whether they actually use OSGi or not.
- New Arquillian integration testing framework for easier testing against remote or docker based fabrics
- Fixes to various things like Java containers, Tomcat and Docker
- Fixes these issues
- AutoScaler can now properly recreate ssh containers if the ssh hosts are specified in the json like in this example plus there is a new autoscale-status CLI command to see how the auto scaler is progressing
- Fixes these 56 issues and enhancements
- New top level Profiles tab in the web console makes it nice and easy to view and search all profiles; filtering by text or tag with nice icons and summary text coming from icon.(svg,png,jpg) and Summary.md files in the wiki
- First spike of Fabric DNS support
- AutoScaler can now properly recreate Java Container and Process Container instances if the process is explicitly killed
- The feature name for the amq: endpoint, mq-fabric-camel has been renamed to camel-amq which is more usual name for camel feature names
- Fixes these 132 issues and enhancements
- Renamed CLI command
fabric:profile-download
tofabric:profile-download-artifacts
- Fixes these 165 issues and enhancements
- Working Java Container for working with Micro Services and Spring Boot
- Great Spring Boot integration
- Support for Apache Tomcat, TomEE and Jetty as web containers
- integration with fabric:watch * and various containers like Java Container, Spring Boot, Tomcat, TomEE, Jetty
- lots more QuickStart examples which are all included in the distribution and turned into archetypes
- new Continuous Deployment commands like profile-import, profile-export and improved mvn fabric8:zip goal that works with multi-maven projects
- Fixes these 136 issues and enhancements
- the script to start a container is now bin/fabric8 and by default it will create a fabric unless you explicitly configure one of the fabric8 environment variables
- added new maven plugin goals (fabric8:agregate-zip, fabric8:zip, fabric8:branch)
- fully working docker support so using the docker profile you can create containers using docker.
- Fixes these 300 issues and enhancements
- first community release integrated into the JBoss Fuse 6.1 product
- includes hawtio as the console
- uses git for configuration; so all changes are audited and versioned and its easy to revert changes.