rohitkrai03

Better Helm Chart installation experience in OpenShift Console using values.schema.json

Introduction

OCP 4.4 introduced native support for Helm Charts including a UI experience in OpenShift Developer Console to install and manage charts.

Release of OCP 4.6 will enhance the Helm experience further more in Developer Console by introducing dynamic form generation in chart installation using values schema.

A chart maintainer can define a schema in values.schema.json file to enable dynamic form chart installation experience in console. A schema is represented as a JSON Schema. It might look something like this:

bmaupin

1. Change apiVersion from:

   - apiVersion: v1

   (or apiVersion: apps.openshift.io/v1)

   to:

tmckayus

Overview: running crc on a remote server

This document shows how to deploy an OpenShift instance on a server using CodeReady Containers (crc) that can be accessed remotely from one or more client machines (sometimes called a "headless" instance). This provides a low-cost test and development platform that can be shared by developers. Deploying this way also allows a user to create an instance that uses more cpu and memory resources than may be available on his or her laptop.

While there are benefits to this type of deployment, please note that the primary use case for crc is to deploy a local OpenShift instance on a workstation or laptop and access it directly from the same machine. The headless setup is configured completely outside of crc itself, and supporting a headless setup is beyond the mission of the crc development team. Please do not ask for changes to crc to support this type of deployment, it will only cost the team time as they politely decline :)

The instructions here were tested with F

Can-Sahin

#!/bin/bash

username="COGNITO_USER_NAME"
password="PASSWORD"
clientid="APP_CLIENT_ID"
region="eu-west-1"
aws_profile="AWS_CLI_PROFILE"

response_json=""
json_field='IdToken'

pedro-hos

Rh-SSO with EAP7 Cluster setup guide.

This installation and configuration guide is intended to use as the main concept of integrating RedHat SSO with mod_cluster only. The guide doesn’t cover full brown cluster setup. For more advanced cluster setup, please refer here.

Requirement

• Red Hat JBoss Core Services Apache HTTP Server 2.4.23 for RHEL 7 x86_64
• EAP 7
• BPMS
• RH-SSO

glenhallworthreadify

const puppeteer = require('puppeteer');

class Webpage {
    static async generatePDF(url) {
        const browser = await puppeteer.launch({ headless: true }); // Puppeteer can only generate pdf in headless mode.
        const page = await browser.newPage();
        await page.goto(url, { waitUntil: 'networkidle', networkIdleTimeout: 5000 }); // Adjust network idle as required. 
        const pdfConfig = {
            path: 'url.pdf', // Saves pdf to disk. 
            format: 'A4',

andreicristianpetcu

An Ansible summary

Jon Warbrick, July 2014, V3.2 (for Ansible 1.7)

Configuration file

intro_configuration.html

First one found from of

yashpatil

This is a quick reference to get to Jolokia statistics urls for JBoss Fuse or JBoss A-MQ statistics. Sometimes, when you are interested in very specific attributes, it's easier to keep monitoring a specific url rather than loading the full Hawtio console.

• List all MBeans
  • GET
  • POST
• Search
• GET

inindev

/* 
 * derivative work of Matheus de Oliveira's json_manipulator.sql
 *   https://gist.github.com/matheusoliveira/9488951 
 *
 *  adapted to support postgresql 9.4 jsonb type
 *  no warranties or guarantees of any kind are implied or offered
 *
 *  license is as Matheus conferred it on 4/9/2015:
 *  matheusoliveira commented on Apr 9
 *    @hannes-landeholm, I'd like to take credit if you share them 

mmoulton

Docker stats collection for collectd

This script can be used to feed collectd with cpu and memory usage statistics for running docker containers using the collectd exec plugin.

This script will report the used and cached memory as well as the user and system cpu usage by inspecting the appropriate cgroup stat file for each running container.

Usage

This script is intented to be executed by collectd on a host with running docker containers. To use, simply configure the exec plugin in collectd to execute the collectd-docker.sh script. You may need to adjust the script to match your particulars, such as the mount location for cgroup.