#IstioCon Taming Istio Configuration with Helm Ryan Michela / @ryanmichela / Salesforce #IstioCon In this talk This is a talk about using Helm with Istio ● Look at helm from a new perspective DEMO #IstioCon Demo - Bookinfo What did we see? ● Single entry point for each service’s configuration ● Install each service with a single command ● Single source of truth for auth and egress policy Everything you need to run a service in the mesh ● Ingress-service ○ Add’s ingress gateway configuration to mesh-service ● Mesh-egress ○ Configures TLS egress and policy ● Auth-policy ○ Configures

6 1.2.6. JMX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.2.7. ActiveMQ (JMX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.2.8. Camel (JMX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . collector: karaf@root()> feature:install decanter-collector-log The log collector doesn’t need any configuration, the installation of the decanter-collector-log feature is enough.  The Decanter log collector

server 4.6.2. JMX MBeanServer 4.7. Log 4.7.1. Configuration files 4.7.2. Log4j v2 support 4.7.3. karaf.log.console property 4.7.4. Commands 4.7.5. JMX LogMBean 4.7.6. Advanced configuration 4.8. Configuration 4.8.2. Files 4.8.3. config:* commands 4.8.4. JMX ConfigMBean 4.9. Artifacts repositories and URLs 4.9.1. Maven URL Handler 4.9.2. Maven configuration commands 4.10. Provisioning 4.10.1. Application Dependent features 4.10.10. Feature configurations 4.10.11. Feature configuration files 4.10.12. Commands 4.10.13. Deployer 4.10.14. JMX FeatureMBean 4.11. Deployers 4.11.1. Blueprint deployer 4.11.2

feature integration 1.2.3. Log Socket 1.2.4. File 1.2.5. EventAdmin 1.2.6. JMX 1.2.7. ActiveMQ (JMX) 1.2.8. Camel (JMX) 1.2.9. Camel Tracer & Notifier 1.2.10. System 1.2.11. Network socket 1.2 quick "ready to go" set of components: • elasticsearch • kibana • the elasticsearch appender • the JMX and log collectors 1.2. Collectors Decanter collectors harvest the monitoring data, and send this 1.0 karaf@root()> feature:install decanter-collector-log The log collector doesn’t need any configuration, the installation of the decanter-collector-log feature is enough. NOTE The Decanter log collector

completely manage the container. • Dynamic Configuration: Apache Karaf provides a set of command dedicated for the management of the configuration files. All configuration files are centralized in the etc folder folder. Any change in a configuration file is taken on the fly. • Advanced Logging System: Apache Karaf supports a large set of Logging framework (slf4j, log4j, etc). Whatever the logging framework you you use, Apache Karaf centralizes the configuration in one file. • Provisioning: Apache Karaf supports a large set of URL where you can install your application (Maven repository, HTTP, file, etc). It also

the status of several Karaf instances (named nodes). Cellar provides dedicated shell commands and JMX MBeans to manage the cluster, and manipulate the resources on the cluster. It’s also possible to automatically installed, providing the etc/hazelcast.xml configuration file. The etc/hazelcast.xml configuration file contains all the core configuration, especially: * the Hazelcast cluster identifiers (group (group name and password) * network discovery and security configuration karaf@root()> cluster: karaf@root()> feature:install cellar-event karaf@root()> feature:install cellar-obr karaf@root()>

automatically installed, providing the etc/hazelcast.xml configuration file. The etc/hazelcast.xml configuration file contains all the core configuration, especially: * the Hazelcast cluster identifiers (group (group name and password) * network discovery and security configuration karaf@root()> cluster: karaf@root()> feature:install cellar-event karaf@root()> feature:install cellar-obr karaf@root()> cluster). 4.2. Network The element in the etc/hazelcast.xml contains all the network configuration. First, it defines the port numbers used by Hazelcast: Second, it defines the mechanism used

wrapper service 5.1. Repository metadata access 6. Maven wrapper service 7. Administration 7.1. JMX 7.2. REST Overview Apache Karaf Cave is an Apache Karaf sub-project. Cave is an implementation KARAF_BASE/cave. You can change the storage location in the etc/org.apache.karaf.cave.server.storage.cfg configuration file: karaf@root()> cave: cave:repositories cave:repository-create cav Administration 7.1. JMX When you install Apache Karaf Cave server, it provides a CaveServerMBean. This MBean uses the following object name: Thanks to this MBean, using any JMX client (like jconsole

driver, so we reuse hive JDBC driver to connect to Kyuubi server. Add repository to your maven configuration file which may reside in $MAVEN_HOME/conf/settings.xml. central location Configuration configuration = new Configuration(); configuration.set(HADOOP_SECURITY_AUTHENTICATION, "kerberos"); UserGroupInformation.setConfiguration(configuration); UserGroupInformation com/docker-for-mac/networking/#known- limitations-use-cases-and-workarounds]. 6.3.1. Configuration 1. Copy a configuration template from Hue Docker image. docker run --rm gethue/hue:latest cat /usr/sha