Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecation exception, normalize capitalization, add links #2567

Merged
merged 1 commit into from
Nov 20, 2024
Merged

Deprecation exception, normalize capitalization, add links #2567

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 14 additions & 4 deletions _docs/technology/responsibilities.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,15 +2,18 @@
parent: technology
layout: docs
sidenav: true
title: What the cloud.gov PaaS offers
title: Cloud.gov responsibilities and deprecation policy
weight: 5
redirect_from:
- /docs/intro/technology/responsibilities/
- /intro/technology/responsibilities/
- /overview/technology/responsibilities/
---

As a Platform as a Service, cloud.gov is responsible for maintenance and security of the cloud.gov platform. Customers are responsible for maintenance and security of their custom code running on the platform.

## Cloud.gov Platform responsibilities

As a Platform as a Service, Cloud.gov is responsible for maintenance and security of the Cloud.gov platform. Customers are responsible for maintenance and security of their custom code running on the platform.

Here's a chart to illustrate this in three example use cases:

Expand All @@ -28,7 +31,7 @@ App #2 uses a [custom buildpack]({{ site.baseurl }}{% link _docs/deployment/cust

App #3 is a Docker setup, where the customer is fully responsible for their Docker container and custom image. [Learn about this feature.]({{ site.baseurl }}{% link _docs/deployment/docker.md %})

cloud.gov is always responsible for the following components at its platform level:
Cloud.gov is always responsible for the following components at its platform level:

* Operating system
* Continuous monitoring
Expand All @@ -39,6 +42,8 @@ cloud.gov is always responsible for the following components at its platform lev
* Logging
* Alerting

**See also**: The Cloud.gov [customer service objectives]({{ site.baseurl }}{% link _docs/overview/customer-service-objectives.md %})

## Deprecation policy

From time to time, it becomes necessary to deprecate a service, feature, or API. Below is our policy for doing so. In the description, `service`
Expand All @@ -55,7 +60,7 @@ Deprecations happen in steps:

Here's an example:

First, cloud.gov determines that the coffee service is not serving customers as well as a new espresso service might, and we decide
First, Cloud.gov determines that the coffee service is not serving customers as well as a new espresso service might, and we decide
to replace the coffee service entirely with the espresso service.
First, we make the espresso service generally available. Next, we send out the general announcement to all of our users. This announcement goes out on April 3rd and states:

Expand All @@ -66,3 +71,8 @@ First, we make the espresso service generally available. Next, we send out the g

After May 3rd, we begin sending emails to users still using the coffee service, at least one message every other week.
Finally, on August 31st, we shut down the last instances of the coffee service.

### Exceptions

Cloud.gov may need to accelerate a deprecation timeline when maintaining a service poses risks to platform
operation. We will note in customer communications when and why we're using an accelerated timeline.
Loading