Skip to content

Commit

Permalink
Merge branch 'master' into document-serviceDomain-pack-field-pcp-935
Browse files Browse the repository at this point in the history
  • Loading branch information
ritawatson committed Sep 11, 2023
2 parents d170284 + 80ee670 commit e5cfb96
Show file tree
Hide file tree
Showing 3 changed files with 102 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/docs-content/clusters/cluster-management/node-pool.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ Ensure you exercise caution when modifying node pools. We recommend creating a [

In Kubernetes, the term "repave" refers to the process of replacing a node with a new node. [Repaving](/glossary-all#repavement) is a common practice in Kubernetes to ensure that nodes are deployed with the latest version of the operating system and Kubernetes. Repaving is also used to replace nodes that are unhealthy or have failed. You can configure the repave time interval for a node pool.

The ability to configure the repave time interval for all node pools except the master pool. The default repave time interval is 900 seconds (15 minutes). You can configure the node repave time interval during the cluster creation process or after the cluster is created. To modify the repave time interval after the cluster is created, follow the [Change a Node Pool](#changeanodepool) instructions below.
The ability to configure the repave time interval for all node pools except the master pool. The default repave time interval is 0 seconds. You can configure the node repave time interval during the cluster creation process or after the cluster is created. To modify the repave time interval after the cluster is created, follow the [Change a Node Pool](#changeanodepool) instructions below.


## Node Pool Configuration Settings
Expand Down Expand Up @@ -48,7 +48,7 @@ The following tables contain the configuration settings for node pools. Dependin
|-----------|-------------|
| **Node pool name** | A descriptive name for the worker pool. |
| **Number of nodes in the pool** | Number of nodes to be provisioned for the node pool. |
| **Node repave interval** | The time interval in seconds between repaves. The default value is 900 seconds (15 minutes). |
| **Node repave interval** | The time interval in seconds between repaves. The default value is 0 seconds. |
| **Additional Labels** | Optional labels apply placement constraints on a pod. For example, you can add a label to make a node eligible to receive the workload. To learn more, refer to the [Overview on Labels](/clusters/cluster-management/taints#overviewonlabels). |
| **Taints** | Sets toleration to pods and allows (but does not require) the pods to schedule onto nodes with matching taints. To learn more, refer to the [Overview on Taints](/clusters/cluster-management/taints#overviewontaints).|
| **Rolling update** | Apply the update policy. **Expand first** launches new nodes and then terminates old notes. **Contract first** terminates old nodes and then launches new ones. |
Expand Down
20 changes: 20 additions & 0 deletions docs/docs-content/release-notes.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,26 @@ tags: ["release-notes"]
---



## September 1, 2023 - Release 4.0.8

This release contains minor bug fixes.

### Bug Fixes

- A bug that caused ARM64 Nvidia Jetson cluster deployment to fail has been resolved.

- The problem with a blank **drop-down Menu** when trying to add a CoxEdge cloud account is resolved with a populated menu.

## August 31, 2023 - Release 4.0.7

This release contains minor bug fixes.

### Bug Fixes

- A problem with Palette retaining original pack values in manifests after users apply modifications has been resolved.


## August 27, 2023 - Release 4.0.0 {#release-4-0}

Palette 4.0.0 introduces new features and improvements, including [Palette VerteX](/vertex) - a FIPS-compliant edition - and the [Virtual Machine Orchestrator](/vm-management) (VMO) which enables unified management of containerized applications and virtual machines in Kubernetes. Additionally, Palette 4.0.0 introduces a new Pack User Interface (UI) that improves the user experience for finding and installing packs. Check out the [Upgrade Notes](/enterprise-version/upgrade) and release notes below to learn more about the new features and improvements in Palette 4.0.0.
Expand Down
80 changes: 80 additions & 0 deletions scripts/url-checker.sh
Original file line number Diff line number Diff line change
@@ -0,0 +1,80 @@
#!/bin/bash

# Set variables for GitHub API and Slack webhook
ACCESS_TOKEN=$ACCESS_TOKEN
OWNER=$OWNER
REPO=$REPO
SLACK_WEBHOOK_URL=$SLACK_WEBHOOK_URL

# Define emoji for each object
EMOJI1=":loudspeaker:"
EMOJI2=":robot:"
EMOJI3=":news:"

# Get the branch name
BRANCH_NAME=$(basename "$GITHUB_REF")

# Get the pull request number for the branch
PR_NUMBER=$(curl -s -H "Authorization: token $ACCESS_TOKEN" \
"https://api.github.com/repos/$OWNER/$REPO/pulls?head=$BRANCH_NAME" | jq -r '.[0].number')

# Check if PR number was found
if [[ -z "$PR_NUMBER" ]]; then
echo "Error: Could not find pull request number for branch '$BRANCH_NAME'"
exit 1
fi

echo "Pull request number: $PR_NUMBER"

# Read JSON file contents into a variable
JSON_CONTENT=$(cat link_report.json)

# Check if JSON file is empty
if [[ -z "$JSON_CONTENT" ]]; then
echo "No broken links found"
exit 0
fi

# Initialize counter for broken links
BROKEN_LINK_COUNT=0

# Format comment with JSON content
COMMENT=":loudspeaker: Broken Docs Links in Production Report :spectro: \n\n This is the weekly report of broken links in production. Please review the report and make the required changes. \n\n *Note*: Some links may be false positives due to redirects behavior.\n\n"

# Loop through the "links" array and concatenate each item into the COMMENT variable
for link in $(echo "${JSON_CONTENT}" | jq -r '.links[] | @base64'); do
url=$(echo "${link}" | base64 --decode | jq -r '.url')
state=$(echo "${link}" | base64 --decode | jq -r '.state')
parent=$(echo "${link}" | base64 --decode | jq -r '.parent')

# Increment counter for broken links if status is not "200"
if [[ "$status" != "200" ]]; then
((BROKEN_LINK_COUNT++))
fi

COMMENT="${COMMENT}\n\n:link: Broken URL: ${url} \n:red_circle: State: ${state} \n:arrow_up: Parent Page: ${parent}\n\n"
done

# Check if no broken links are found
if [[ "$BROKEN_LINK_COUNT" -eq 0 ]]; then
COMMENT=":tada: No broken links found in the production report :tada:\n\nGreat job team! Keep up the good work!\n\nSource: :github: - librarium"
else
# Add broken link count to the comment
COMMENT="${COMMENT}\n\n Total count of broken URLs: ${BROKEN_LINK_COUNT}\n\n Source: :github: - librarium"
fi

# Post the comment to the Slack webhook
curl -X POST -H 'Content-type: application/json' --data "{\"text\":\"${COMMENT}\"}" $SLACK_WEBHOOK_URL

if [[ "${DEBUG}" == "true" ]]; then
echo "GitHub API URL: ${GITHUB_API_URL}"
echo "Pull Request Number: ${PR_NUMBER}"
echo "Repository Owner: ${REPO_OWNER}"
echo "Repository Name: ${REPO_NAME}"
echo "JSON content:"
echo "$json"
echo "COMMENT content:"
echo "$COMMENT"
fi

echo "Posting comment to pull request #$PR_NUMBER to Slack webhook"

0 comments on commit e5cfb96

Please sign in to comment.