You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: src/docs/app-monitoring/sysdig-monitor-setup-team.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Effective monitoring and alerting are crucial components of maintaining a robust
27
27
28
28
The Sysdig Teams Operator runs in the cluster and enables a team to create and manage access to a dedicated Sysdig Team account for BC Gov Private Cloud PaaS users. The team is scoped to the OpenShift namespaces that belong to the team. Sysdig also provides a default dashboard to identify system [resources, limits, and actual usage](../automation-and-resiliency/openshift-project-resource-quotas.md).
29
29
30
-
For more information on Sysdig Monitor, see [Monitoring with Sysdig](https://digital.gov.bc.ca/delivery/cloud/private/products-tools/sysdig/)
30
+
For more information on Sysdig Monitor, see [Monitoring with Sysdig](https://digital.gov.bc.ca/technology/cloud/private/products-tools/sysdig/)
Copy file name to clipboardexpand all lines: src/docs/automation-and-resiliency/namespace-recovery-and-responsibilities.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ sort_order: 8
20
20
21
21
# Product team recovery best practices and responsibilities
22
22
23
-
If you haven't done so already, take a look at our [Memorandum of understanding (MoU)](https://digital.gov.bc.ca/delivery/cloud/private/onboard/#memorandum). This document covers the more technical side of *how* to follow through on the responsibilities outlined in that document.
23
+
If you haven't done so already, take a look at our [Memorandum of understanding (MoU)](https://digital.gov.bc.ca/technology/cloud/private/onboard/#memorandum). This document covers the more technical side of *how* to follow through on the responsibilities outlined in that document.
24
24
25
25
You can additionally review the [Responsibility Assignment Table (RACI)](https://digital.gov.bc.ca/wp-content/uploads/RACI-Shared-responsibilities-model-for-the-Private-cloud-OpenShift-platform.pdf). This will provide you with deeper detail, a view of roles and shared responsibilities between your team and the Private cloud team. This table provides a clear breakdown of these shared responsibilities for the Private cloud OpenShift platform, outlining key tasks, decision-making authority, and support functions.
Copy file name to clipboardexpand all lines: src/docs/build-deploy-and-maintain-apps/build-an-application.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ This document outlines the best practices for building applications on OpenShift
41
41
## Requirements to build your application
42
42
Here are ten common practices for building applications in a cloud native way that we strongly suggest your team follow before building an application on OpenShift:
43
43
44
-
1.**Learn OpenShift basics**: Understand OpenShift's core concepts including projects, pods, services, routes and deployments. Sign up for the [OpenShift training](https://digital.gov.bc.ca/delivery/cloud/private/support/#platform)
44
+
1.**Learn OpenShift basics**: Understand OpenShift's core concepts including projects, pods, services, routes and deployments. Sign up for the [OpenShift training](https://digital.gov.bc.ca/technology/cloud/private/support/#platform)
45
45
46
46
2.**Learn Kubernetes fundamentals**: OpenShift is built on Kubernetes, so basic knowledge is essential. Get comfortable using the [Kubernetes documentation](https://kubernetes.io/docs/home/).
47
47
@@ -117,7 +117,7 @@ Most applications need some data to persist across different sessions or connect
117
117
118
118
## Best practices for creating your image
119
119
120
-
Once your application code is ready, you'll need to build an image in order to deploy it to a pod on the OpenShift cluster. [OpenShift 101](https://digital.gov.bc.ca/delivery/cloud/private/support/openshift-101/) training provides a step-by-step walkthrough to build an image. If you haven't taken it already, please do so!
120
+
Once your application code is ready, you'll need to build an image in order to deploy it to a pod on the OpenShift cluster. [OpenShift 101](https://digital.gov.bc.ca/technology/cloud/private/support/openshift-101/) training provides a step-by-step walkthrough to build an image. If you haven't taken it already, please do so!
121
121
This section will primarily focus on best practices for building your image - 'what you should do' rather than 'how to do it'.
Copy file name to clipboardexpand all lines: src/docs/build-deploy-and-maintain-apps/maintain-an-application.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -450,11 +450,11 @@ Before scheduled changes to the platform and shared services occur, the Platform
450
450
451
451
Moreover, it's advisable for all team members to remain engaged with the community through the following channels:
452
452
453
-
- Subscribe to [Platform Services Newsletters](https://digital.gov.bc.ca/delivery/cloud/private/internal-resources/subscribe/) so that you will receive email notifications for upcoming changes, as well as [the Platform Community MeetUp Event](https://digital.gov.bc.ca/delivery/cloud/private/team/#stay) every 3 weeks for platform updates and technical demos.
453
+
- Subscribe to [Platform Services Newsletters](https://digital.gov.bc.ca/technology/cloud/private/internal-resources/subscribe/) so that you will receive email notifications for upcoming changes, as well as [the Platform Community MeetUp Event](https://digital.gov.bc.ca/technology/cloud/private/team/#stay) every 3 weeks for platform updates and technical demos.
454
454
455
455
- Monitor [Rocket.Chat #devops-alerts channel](https://chat.developer.gov.bc.ca/channel/devops-alerts) for service alerts and status updates. Rocket.Chat serves as the main communication method for teams on the platform to get help, share knowledge and information, and build up the community.
456
456
457
-
- Take a look at [common platform requests](https://digital.gov.bc.ca/delivery/cloud/private/support/#common) . This section can be helpful to your team to discover the most commonly searched-for tasks, with links to additional instructions.
457
+
- Take a look at [common platform requests](https://digital.gov.bc.ca/technology/cloud/private/support/#common) . This section can be helpful to your team to discover the most commonly searched-for tasks, with links to additional instructions.
458
458
459
459
---
460
460
## Managing impacts of personnel changes
@@ -468,9 +468,9 @@ The changes and the resulting loss of expertise have a significant impact on the
468
468
469
469
When a new member joins your team, they should go through a similar onboarding process as any other person joining the OpenShift platform. Along with getting familiar with the specific application(s) supported by their new team, they should also:
470
470
471
-
* Attend [OpenShift 101](https://digital.gov.bc.ca/delivery/cloud/private/support/openshift-101/) and [OpenShift 201](https://digital.gov.bc.ca/delivery/cloud/private/support/openshift-201/) training
472
-
* Go through the [onboarding process](https://digital.gov.bc.ca/delivery/cloud/private/onboard/) which can be done with your team's Product owner or by scheduling a meeting with a member of the Platform team.
473
-
* Join the community on [Rocket.Chat](../../bc-developer-guide/rocketchat/steps-to-join-rocketchat/), [Stack Overflow](https://digital.gov.bc.ca/delivery/cloud/private/support/#community) and our [Platform Community Meetups](https://digital.gov.bc.ca/delivery/cloud/private/team/#stay)
471
+
* Attend [OpenShift 101](https://digital.gov.bc.ca/technology/cloud/private/support/openshift-101/) and [OpenShift 201](https://digital.gov.bc.ca/technology/cloud/private/support/openshift-201/) training
472
+
* Go through the [onboarding process](https://digital.gov.bc.ca/technology/cloud/private/onboard/) which can be done with your team's Product owner or by scheduling a meeting with a member of the Platform team.
473
+
* Join the community on [Rocket.Chat](../../bc-developer-guide/rocketchat/steps-to-join-rocketchat/), [Stack Overflow](https://digital.gov.bc.ca/technology/cloud/private/support/#community) and our [Platform Community Meetups](https://digital.gov.bc.ca/technology/cloud/private/team/#stay)
474
474
*[Obtain access](https://digital.gov.bc.ca/cloud/private/support/) to all relevant namespaces, repositories and other services. Please go to the section: Report and incident > Common platform requests section. Remember to also update the [Platform Product Registry](https://registry.developer.gov.bc.ca/), if needed.
Copy file name to clipboardexpand all lines: src/docs/platform-architecture-reference/openshift-network-policies.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ For a connection from a source pod to a destination pod to be allowed, both the
53
53
By using network policies declarative YAML this code becomes part of your application, ensuring the consistency of “single source of truth” from your codebase.
54
54
55
55
From OpenShift version 4.10, CLAB, KLAB, SILVER, GOLD, GOLD-DR clusters are now supporting **limited Egress**(see below notes) network policies.
56
-
KLAB2 and Emerald clusters use a different SDN technology (VMWare NSX-T) which also DOES support (and requires) Egress Network Policies. Details on NSX Networking can be found in the [IDIR protected content area of the Private Cloud website - Guide for Emerald teams](https://digital.gov.bc.ca/delivery/cloud/private/internal-resources/emerald/).
56
+
KLAB2 and Emerald clusters use a different SDN technology (VMWare NSX-T) which also DOES support (and requires) Egress Network Policies. Details on NSX Networking can be found in the [IDIR protected content area of the Private Cloud website - Guide for Emerald teams](https://digital.gov.bc.ca/technology/cloud/private/internal-resources/emerald/).
Copy file name to clipboardexpand all lines: src/docs/platform-architecture-reference/platform-architecture-diagram.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ Last updated: **May 8, 2024**
23
23
24
24
The platform architecture diagram provides a clear visual representation of the layout within the datacentre. It showcases the locations of different clusters and outlines the diverse range of services and features that each cluster offers.
25
25
26
-
1.[View the diagram](https://digital.gov.bc.ca/delivery/cloud/private/internal-resources/diagram/) (protected by IDIR login).
26
+
1.[View the diagram](https://digital.gov.bc.ca/technology/cloud/private/internal-resources/diagram/) (protected by IDIR login).
27
27
28
28
2. After login, depending on the browser you use, it's possible you will be redirected to the https://digital.gov.bc.ca main page, if this happens, please try the link above once more and you should have access to view the diagram.
Copy file name to clipboardexpand all lines: src/docs/platform-architecture-reference/sre-reference-for-app-on-different-cluster.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -9,16 +9,16 @@ This document guides application teams deploying applications across different h
9
9
-**Emerald Cluster**: Tailored for applications requiring enhanced security features, specifically for Protect C project applications
10
10
11
11
## SLA expectations per cluster
12
-
For detailed SLA expectations per cluster, please refer to the official [Hosting tiers SLA documentation](https://digital.gov.bc.ca/delivery/cloud/private/products-tools/hosting-tiers/).
12
+
For detailed SLA expectations per cluster, please refer to the official [Hosting tiers SLA documentation](https://digital.gov.bc.ca/technology/cloud/private/products-tools/hosting-tiers/).
13
13
14
14
## Impact of Vault and Artifactory on application availability
15
15
Vault and Artifactory are crucial components hosted on the Gold cluster, used for secret management and as a image repository manager, respectively. The availability and performance of these services can directly impact the applications depending on them.
16
16
17
17
However, it's important to note:
18
18
19
19
-**SLA for Vault and Artifactory**: Detailed SLA information for these services can be found here:
-**Potential impact on availability**: While Vault and Artifactory have robust failover mechanisms, their SLAs are not always align with the Gold cluster's 99.95% availability. This discrepancy can be attributed to maintenance requirements, service-specific risks, and other operational nuances
23
23
-**Mitigating downtime impact**: Applications hosted in the Gold cluster benefit from robust failover configurations that support high availability, even during temporary outages of Vault or Artifactory. By implementing strategic deployment practices—such as caching secrets, pre-pulling images and failover strategy, teams can minimize dependency on real-time access to these services, ensuring that applications remain operational throughout any service disruptions.
Copy file name to clipboardexpand all lines: src/docs/platform-automation/automated-scaling.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -72,7 +72,7 @@ Before you scale your pods back up, make sure to fix the underlying issues that
72
72
73
73
If your application hasn't been updated in over a year, your technical team should create a new image. This ensures that your application can benefit from any security patches released in the past year. It's highly probable that your image has critical security vulnerabilities if it hasn't been updated for more than a year.
74
74
75
-
Maintaining your application is part of the [Memorandum of Understanding](https://digital.gov.bc.ca/delivery/cloud/private/onboard/#memorandum) that teams working on the platform agree to. More detailed docs on [maintaining an image](../build-deploy-and-maintain-apps/maintain-an-application.md#maintain-images) are also available.
75
+
Maintaining your application is part of the [Memorandum of Understanding](https://digital.gov.bc.ca/technology/cloud/private/onboard/#memorandum) that teams working on the platform agree to. More detailed docs on [maintaining an image](../build-deploy-and-maintain-apps/maintain-an-application.md#maintain-images) are also available.
76
76
77
77
Once you have fixed these issues, you can follow the instructions in [RedHat’s documentation on editing deployments](https://docs.openshift.com/container-platform/4.12/applications/deployments/deployment-strategies.html#odc-editing-deployments_rolling-strategy) to scale your applications back up again.
78
78
@@ -94,5 +94,5 @@ Be aware that if you scale your deployment back up without addressing the underl
94
94
## Related pages
95
95
96
96
- [RedHat’s documentation on editing deployments](https://docs.openshift.com/container-platform/4.12/applications/deployments/deployment-strategies.html#odc-editing-deployments_rolling-strategy)
97
-
- [Memorandum of Understanding](https://digital.gov.bc.ca/delivery/cloud/private/onboard/#memorandum)
97
+
- [Memorandum of Understanding](https://digital.gov.bc.ca/technology/cloud/private/onboard/#memorandum)
98
98
- [Maintaining an image](../build-deploy-and-maintain-apps/maintain-an-application.md#maintain-images)
0 commit comments