#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

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 4.3 Import the example configuration (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 4.4 Start Baetyl . . . . . . . . . . . . . . . . . . . . . 26 5 Build Baetyl From Source 29 5.1 Environment Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 5.2 Source Code 31 6 Baetyl Configuration Interpretation 35 6.1 Master Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 6.2 Application Configuration . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 4.3 Import the example configuration (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 4.4 Start Baetyl 29 6 Baetyl Configuration Interpretation 35 6.1 Master Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 6.2 Application Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 6.3 Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 6.4 baetyl-function-python

the example configuration (optional) Start Baetyl Verify successful installation Build Baetyl From Source Environment Configuration Source Code Compilation Guides Baetyl Configuration Interpretation Interpretation Master Configuration Application Configuration baetyl-agent Configuration baetyl-hub Configuration baetyl-function-manager Configuration baetyl-function-python Configuration baetyl-remote-mqtt Configuration Configuration baetyl-timer Configuration Device connect to Baetyl with Hub service Workflow Connection Test Message transferring among devices with Local Hub Service Workflow Message Routing Test Message

Baetyl Design Contributing Installation Quick Install Baetyl Install from source Guides Baetyl Configuration Interpretation Device connect to Hub Service Message transferring among devices with Hub Service baetyl-remote-mqtt is used to bridge two MQTT Servers for message synchronization and supports configuration of multiple message route rules. ; The official module baetyl-function-manager provides computing the Service, can be a read-only directory, such as a directory for placing resources such as configuration, certificates, scripts, etc., or a writable directory to persist data, such as logs and database

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.1. Environment 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 4.10.2. OSGi 4.10.3. Feature and resolver Feature bundles 4.10.9. 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

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

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 order to work, your Apache Karaf Pax Logging configuration should contain this appender. The default Apache Karaf etc/org.ops4j.pax.logging.cfg configuration file is already fine: log4j.rootLogger = default etc/org.apache.karaf.decanter.collector.log.socket.cfg configuration file containing: # # Decanter Log/Log4j Socket collector configuration # #port=4560 #workers=10 • the port property defines the

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 order to work, your Apache Karaf Pax Logging configuration should contain this appender. The default Apache Karaf etc/org.ops4j.pax.logging.cfg configuration file is already fine: If you want, you can installs the collector and a default etc/ org.apache.karaf.decanter.collector.log.socket.cfg configuration file containing: • the port property defines the port number where the collector is bound and