The update to the new upstream logging implementation has been completed. We measured the log duplication period to be around 1 minute. There should not be any additional impacts to customers during the rest of the upgrade process.
The final upgrade to version 13 of cf-deployment will take hours to finish. It should be complete during the day on Thursday. There should be no impact to customers as the final deployments complete.
Posted Aug 05, 2020 - 18:03 EDT
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Aug 05, 2020 - 10:30 EDT
Update
Note: This maintenance has been moved to August 5th.
Posted Jul 29, 2020 - 18:58 EDT
Scheduled
Note: This maintenance has been moved to August 5th.
This message is to let you know about the upcoming upgrade to v13 of cf-deployment on 05 August 2020. The original update scheduled on 14 July was rescheduled as a bug was discovered in the upstream release.
What is happening?
On August 5, we will be upgrading cloud.gov to version 13 of the upstream Cloud Foundry release called cf-deployment. This release contains changes that may impact users.
cloud.gov is largely based on the open source Cloud Foundry project. We frequently test and deploy upstream releases from the open source community to bring platform updates, security fixes, and new features to our customers. The vast majority of these releases are transparent to our users.
What is the impact to cloud.gov customers during the upgrade?
We have taken significant steps to minimize the impact of the upstream changes on cloud.gov customers. However, during the upgrade there will be a small period where you will see duplicate log entries in Kibana, log drains, or when tailing logs using `cf logs`. This period of time should be less than 15 minutes. You should not experience any abnormal log loss during this time.
We have opted for this approach to ensure you do not incur log loss. We have extensively tested this methodology in our development and staging environments and are confident this is the least impactful way to absorb the upstream changes we rely on.
What is the impact to cloud.gov customers after the upgrade?